-
Notifications
You must be signed in to change notification settings - Fork 330
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
create "default" namespace by default #56
Comments
Hey @markmark206 any update on this? Is there a good workaround when doing an automated deployment that doesn't require calling |
we've come to the conclusion that for our helm charts we should not create a default namespace by default because having a default namespace is only a convenience for development - which is why it's automatically created when running temporal via docker-compose. additionally since namespaces cannot currently be deleted we would be adding something that is more likely to cause accidental problems in production environments but that has no way of being removed (as is still an issue with kubernetes default namespaces and one we'd like to avoid if we can). |
I have a related question. Even if the default namespace is not created automatically, should the helm chart not have a way to configure some pre-created namespaces via the values ? |
agreed, even though this shouldn't be a the default behaviour there should be a parameter available on the helmchart to do it |
Would you all accept a PR to fix this? |
#420 opened to track this. PRs accepted. |
When running the system via
docker-compose
(e. g. https://github.com/temporalio/temporal/blob/master/docker/docker-compose.yml), the system starts up withdefault
namespace already existing. However, this is not the case when deploying the system via helm chart.Please add default namespace when deploying temporal via helm chart.
PS Thanks to Remy for reporting this!
The text was updated successfully, but these errors were encountered: