Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

stable/mongodb: override namespace for mongo deployment #20440

Closed
benjamin-wright opened this issue Jan 30, 2020 · 6 comments
Closed

stable/mongodb: override namespace for mongo deployment #20440

benjamin-wright opened this issue Jan 30, 2020 · 6 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@benjamin-wright
Copy link

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 to values.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.

@juan131
Copy link
Collaborator

juan131 commented Jan 31, 2020

Hi @benjamin-wright

Thanks so much for opening this issue! I added some comments in the PR you created.

@stale
Copy link

stale bot commented Mar 1, 2020

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.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 1, 2020
@stale
Copy link

stale bot commented Mar 15, 2020

This issue is being automatically closed due to inactivity.

@stale stale bot closed this as completed Mar 15, 2020
@benjamin-wright
Copy link
Author

bump

@juan131
Copy link
Collaborator

juan131 commented Mar 31, 2020

Hi @benjamin-wright

Given the stable deprecation timeline, this Bitnami maintained Helm chart was deprecated and moved to bitnami/charts some weeks ago. Please visit the bitnami/charts GitHub repository to create Issues or PRs.

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.

@benjamin-wright
Copy link
Author

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!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants