You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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:
The text was updated successfully, but these errors were encountered: