-
Notifications
You must be signed in to change notification settings - Fork 23
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
Respect Helm namespace #331
Comments
Thank you for your contribution! This issue has been automatically marked as |
This issue is tracked here now, sorry for the long delay! |
I believe this was closed inadvertently. |
Sorry, I fixed the link in my previous comment. The underlying issue here is the kustomize support, solving that would solve this issue as well, and that is why I closed it. |
Is your feature request related to a problem? Please describe.
Deploying the vault-operator Helm chart via Kustomize's
helmCharts
feature, all of the resources end up in thedefault
namespace. It appears that the Helm chart doesn't specify a namespace on any of its resources.Describe the solution you'd like
If I specify a namespace, I'd like vault-operator to deploy into that namespace.
Describe alternatives you've considered
I'm currently using 9
patchesJson6902
patches to move resources into the correct namespace.Additional context
It looks like other Helm charts include this in every namespaced resource's
metadata
:The text was updated successfully, but these errors were encountered: