-
Notifications
You must be signed in to change notification settings - Fork 70
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
Namespace cannot be overwritten with helm template #152
Comments
yes please. we install these components into a namespace called |
Any news on this ? It has been 7 months... |
knutejohKLP
added a commit
to knutejohKLP/istio-csr
that referenced
this issue
Dec 14, 2022
knutejohKLP
added a commit
to knutejohKLP/istio-csr
that referenced
this issue
Dec 14, 2022
…-manager#152. Signed-off-by: Knut-Erik Johnsen <knut-erik.johnsen@klp.no>
jetstack-bot
added a commit
that referenced
this issue
Feb 17, 2023
Add support for setting namespace for istio control plane. Fixes #152
knutejohKLP
added a commit
to knutejohKLP/istio-csr
that referenced
this issue
Feb 19, 2023
…-manager#152. Signed-off-by: Knut-Erik Johnsen <knut-erik.johnsen@klp.no> Signed-off-by: Knut-Erik Johnsen <knut-erik.johnsen@klp.no>
👍🏻 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be awesome if the chart allowed overwriting the namespace of the:
Currently, when doing:
into a kustomization, and kubectl apply -k of the resulting yaml, those resources end up in the default namespace.
Preferably the chart would define a way to set the namespace at the template time.
The text was updated successfully, but these errors were encountered: