-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gateway UI assumes openfaas-fn is the default namespace #1407
Comments
/assign: me |
alexellis
changed the title
Gateway UI assumes openfaas-fn is the defeault function namespace
Gateway UI assumes openfaas-fn is the default namespace
Dec 17, 2019
@LucasRoesler and @alexellis do we think this is ok? the backend isnt returning my "default" namespace first? |
@Waterdrips i think we can update he providers to always put the default namespace first |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My actions before raising this issue
If I deploy openfaas and set the default function namespace to something that is not
openfass-fn
the gateway UI will not be able to deploy any functions. it returns an errorThis error is correct, but not expected.
Expected Behaviour
The UI should request the list of namespaces and use the first one in the list as the default.
This of course requires that the api return the configured default as the first value
Current Behaviour
The ui can not deploy functions unless you explicitly deploy with the
openfaas-fn
namespace.Steps to Reproduce (for bugs)
openfaas-5.3.8
but setnamespace=not-default-openfaas
andfunctionNamespace=not-default-openfaas-fn
NodeInfo
Context
Your Environment
Are you using Docker Swarm or Kubernetes (FaaS-netes)?
faas-netes
Operating System and version (e.g. Linux, Windows, MacOS):
osx
The text was updated successfully, but these errors were encountered: