We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When you set spec.targetNamespace the HelmRelease is successfully installed into that namespace
spec.targetNamespace
HelmRelease
If you change that field afterwards, the HelmRelease will be installed into the new namespace, but also be left in the old namespace
.spec.targetNamespace=kube-system
spec.targetNamespace=default
helm list -A
It should delete the old helm release, just like when I delete a HelmRelease
(I don't expect any move magic, delete and recreate is what I'm after)
move
No response
N/A
helm-controller:v0.20.1
The text was updated successfully, but these errors were encountered:
hiddeco
Successfully merging a pull request may close this issue.
Describe the bug
When you set
spec.targetNamespace
theHelmRelease
is successfully installed into that namespaceIf you change that field afterwards, the
HelmRelease
will be installed into the new namespace, but also be left in the old namespaceSteps to reproduce
HelmRelease
with.spec.targetNamespace=kube-system
spec.targetNamespace=default
helm list -A
Expected behavior
It should delete the old helm release, just like when I delete a HelmRelease
(I don't expect any
move
magic, delete and recreate is what I'm after)Screenshots and recordings
No response
OS / Distro
N/A
Flux version
helm-controller:v0.20.1
Flux check
N/A
Git provider
No response
Container Registry provider
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: