Skip to content
This repository has been archived by the owner on Jul 22, 2019. It is now read-only.

Deleting a chart using helm CLI does not delete helmrelease #20

Open
sozercan opened this issue Jan 30, 2018 · 1 comment
Open

Deleting a chart using helm CLI does not delete helmrelease #20

sozercan opened this issue Jan 30, 2018 · 1 comment

Comments

@sozercan
Copy link

Using helm delete releaseName --tiller-namespace=kubeapps from CLI should also delete the helmrelease

@anguslees
Copy link
Contributor

anguslees commented Feb 5, 2018

This is difficult and subtle, and the short answer is:
Don't do that, use kubectl plugin helm delete releaseName instead.

Currently the CRD is treated as the authoritative definition of what should be in the cluster (eg: if someone creates/removes HelmRelease objects while the controller is down, then on restart the controller should tell tiller to install/delete charts until the two match again). If we start trying to also discover what tiller is doing and reflect that back in the HelmRelease state, then now we have no authoritative source and can't reliably resolve differences.

This sucks because it's such an obvious thing to want to support :( I will have to think about other options..

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants