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

Allow auto creation of namespaces when possible #21

Open
lewismarshall opened this issue Oct 14, 2015 · 3 comments
Open

Allow auto creation of namespaces when possible #21

lewismarshall opened this issue Oct 14, 2015 · 3 comments
Assignees

Comments

@lewismarshall
Copy link
Contributor

At the moment, kb8or will deploy to namespaces based on kb8or environment name. It will fail on versions of kubernetes where namespaces need to be explicitly created.

Allow namespaces to be created automatically if they don't exist e.g. when deploying to nfidd-vagrant, pass kubectl this yaml:

apiVersion: v1
kind: Namespace
metadata:
  name: nfidd-vagrant
@vaijab
Copy link

vaijab commented Oct 14, 2015

This is more of a policy issue. IMO if cluster denies namespace auto creation, then should kb8or be creating them?

@lewismarshall
Copy link
Contributor Author

Kb8or will not be arbitrarily creating any namespace - only one for the kb8or environment in use..

If the policy is not to allow creation of Namespaces, then that's fine too - kb8or won't be able to create them.

If this isn't implemented then the user would only do it immediately by creating a Namespace document manually and adding it to either the kb8or deploy or with kubectl directly.

@lewismarshall lewismarshall self-assigned this Nov 18, 2015
@lewismarshall
Copy link
Contributor Author

Just upgraded to kerbernetes v1.1.1 and the namespace is no longer dynamically created. Will implement this now.

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

2 participants