Skip to content
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

Closed
1 of 3 tasks
LucasRoesler opened this issue Dec 17, 2019 · 5 comments
Closed
1 of 3 tasks

Gateway UI assumes openfaas-fn is the default namespace #1407

LucasRoesler opened this issue Dec 17, 2019 · 5 comments
Assignees

Comments

@LucasRoesler
Copy link
Member

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 error

unable create Deployment: namespaces "openfaas-fn" not found

image

This 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)

  1. Deploy on kubernetes with the latest helm chart openfaas-5.3.8 but set namespace=not-default-openfaas and functionNamespace=not-default-openfaas-fn
  2. Open the gateway ui
  3. Try to deploy 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

@Waterdrips
Copy link
Contributor

/assign: me

@alexellis 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
@alexellis
Copy link
Member

Ref: openfaas/faas-netes#511

@Waterdrips
Copy link
Contributor

Waterdrips commented Dec 17, 2019

The UI should request the list of namespaces and use the first one in the list as the default.

@LucasRoesler and @alexellis do we think this is ok? the backend isnt returning my "default" namespace first?

@LucasRoesler
Copy link
Member Author

@Waterdrips i think we can update he providers to always put the default namespace first

@Waterdrips
Copy link
Contributor

/close

this should have been closed by #1409 but i put the same issue (#1408 ) in the close section twice

@derek derek bot closed this as completed Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants