Skip to content
This repository has been archived by the owner on Jul 16, 2021. It is now read-only.

Allow specifying a namespace other than "default" when creating deployments #327

Closed
arapulido opened this issue Jul 24, 2017 · 1 comment · Fixed by #336
Closed

Allow specifying a namespace other than "default" when creating deployments #327

arapulido opened this issue Jul 24, 2017 · 1 comment · Fixed by #336
Milestone

Comments

@arapulido
Copy link

Right now, when creating deployments with Monocular, it is not possible to specify the namespace, so all deployments happen in the default namespace.

It would be good to be able to specify a different namespace

@prydonius
Copy link
Member

Should Monocular show existing namespaces, or just provide a textbox to enter the name of the namespace? Although a dropdown of existing namespaces would be nice, it means Monocular will require special RBAC permissions to query the Kubernetes API for namespaces. A textbox doesn't require this as it will just be passed to Tiller.

In the future, we want to add the ability to view/modify resources created by Monocular, so eventually we will require RBAC permissions, I think it's just a question of whether we do this sooner or later.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants