helm-classic
helm-classic copied to clipboard
Proposal: tracking an installation
With the current implementation, helm remove
removes only the units which are listed in the
current chart. So, if a refactoring in a chart may results in losing track of some pods. There are some approaches to solve this:
- Generating a random token per installation, and injecting
installation-id: $random-token
into labels of all the units which are getting installed. So theremove
command will expect this token and query the units with this token in the given namespace of the kubernetes cluster. - Allowing the caller to inject labels through CLI (and code, for tools which use helm as their package manager).
I know this can also be addressed by the templating solution, but then we have to change all the charts to be sure that there wouldn't be any zombie unit in our cluster.
I'm interested to contribute on this issue. Which approach do you believe is more suitable for helm?