Skip to content
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

HelmRelease targetNamespace change doesn't delete old release #471

Closed
1 task done
cwrau opened this issue Apr 25, 2022 · 0 comments · Fixed by #738
Closed
1 task done

HelmRelease targetNamespace change doesn't delete old release #471

cwrau opened this issue Apr 25, 2022 · 0 comments · Fixed by #738
Assignees
Labels
enhancement New feature or request

Comments

@cwrau
Copy link
Contributor

cwrau commented Apr 25, 2022

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

  1. Create HelmRelease with .spec.targetNamespace=kube-system
  2. Wait for reconcilation
  3. Change spec.targetNamespace=default
  4. Wait for reconcilation
  5. 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

  • I agree to follow this project's Code of Conduct
@stefanprodan stefanprodan transferred this issue from fluxcd/flux2 Apr 29, 2022
@hiddeco hiddeco self-assigned this Jun 7, 2022
@hiddeco hiddeco added the enhancement New feature or request label Jun 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants