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

kompose up always deploys to default namespace #162

Closed
kadel opened this issue Sep 20, 2016 · 3 comments · Fixed by #164
Closed

kompose up always deploys to default namespace #162

kadel opened this issue Sep 20, 2016 · 3 comments · Fixed by #164
Assignees

Comments

@kadel
Copy link
Member

kadel commented Sep 20, 2016

I have created new namespase and set it as default namespace for kubectl.
When I do kubectl create ... it creates object in that namespace.

But when I do kompose up it still deploys to default namespace.

@kadel kadel added the bug label Sep 20, 2016
@ngtuna
Copy link
Contributor

ngtuna commented Sep 20, 2016

👍 Exactly that's not a bug but enhancement :-) Actually for kompose up I'm fixing the default namespace. Let me take this one by investigating the default namespace config from kubectl.

@ngtuna ngtuna self-assigned this Sep 20, 2016
@kadel
Copy link
Member Author

kadel commented Sep 20, 2016

I've started to investigating that, as this blocks me from implementing kompose up for openshift :-(

@ngtuna
Copy link
Contributor

ngtuna commented Sep 20, 2016

Ah that's okay. So I make a handover to you.

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

Successfully merging a pull request may close this issue.

2 participants