-
Notifications
You must be signed in to change notification settings - Fork 16.7k
stable/mongodb: override namespace for mongo deployment #20440
Comments
Thanks so much for opening this issue! I added some comments in the PR you created. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. |
bump |
Given the In this issue (#20969), we tried to explain more carefully the reasons and motivations behind this transition, please don't hesitate to add a comment in this issue if you have any question related to the migration itself. |
Hi @juan131, Ah, sorry, I either missed the deprecation notice on the mongo chart or hadn't noticed it go up in the mean time. Will transfer my suggestion across, thanks! |
It would be very useful if we could pass a namespace for deployment through to the mongodb chart as a value. This would enable umbrella charts to deploy multi-namespace applications in a declarative manner, i.e. without multiple helm charts or multiple calls to helm install/upgrade with different components enabled / disabled.
The proposed change would add
namespaceOverride
tovalues.yaml
, which would default to nil. If supplied, all templates would be deployed into the provided namespace, except for the prometheus service monitor if its own override is also supplied. This would maintain backwards compatibility with the current approach, but would provide the option of changing the deployment namespace when necessary / beneficial.The text was updated successfully, but these errors were encountered: