Describe the bug
When you set spec.targetNamespace the HelmRelease is successfully installed into that namespace
If you change that field afterwards, the HelmRelease will be installed into the new namespace, but also be left in the old namespace
Steps to reproduce
- Create
HelmRelease with .spec.targetNamespace=kube-system
- Wait for reconcilation
- Change
spec.targetNamespace=default
- Wait for reconcilation
- Observe 2 "real" helm releases ->
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
Describe the bug
When you set
spec.targetNamespacetheHelmReleaseis successfully installed into that namespaceIf you change that field afterwards, the
HelmReleasewill be installed into the new namespace, but also be left in the old namespaceSteps to reproduce
HelmReleasewith.spec.targetNamespace=kube-systemspec.targetNamespace=defaulthelm list -AExpected behavior
It should delete the old helm release, just like when I delete a HelmRelease
(I don't expect any
movemagic, 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