You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run the fn ui via the helm chart in kubernetes and add an ingress to connect to the ui, it uses the cluster-internal FN_API_URL for running queries against the fn-api from the user's browser. This service is not available externally as long as there is no ingress configuration.
I think it should either use some proxying through the fn-ui, or allow an FN_EXTERNAL_API_URL to be set that will be used in these contexts. In my case, the fn api is available on fn-api.local. I am running this stuff within minikube for local development.
The text was updated successfully, but these errors were encountered:
When I run the fn ui via the helm chart in kubernetes and add an ingress to connect to the ui, it uses the cluster-internal FN_API_URL for running queries against the fn-api from the user's browser. This service is not available externally as long as there is no ingress configuration.
I think it should either use some proxying through the fn-ui, or allow an FN_EXTERNAL_API_URL to be set that will be used in these contexts. In my case, the fn api is available on
fn-api.local
. I am running this stuff within minikube for local development.The text was updated successfully, but these errors were encountered: