Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Helm keeps track of releases and their revisions by creating a kubernetes Secret each time a chart is installed, upgraded etc. These are of course useful in case you want to rollback, but they do p...
#2: Post edited
Helm delete old releases
- Helm delete old release revisions
Helm keeps track of installed (and previous) releases by creating a kubernetes `Secret` each time a chart is installed, upgraded etc. These are of course useful in case you want to rollback, but they do pile up.**How to prune old helm chart releases from a cluster**, when you're confident you no longer want to return to them?- *(Just deleting the kubernetes secrets would work, but I suspect there's a more elegant way out there.)*
- Helm keeps track of releases and their revisions by creating a kubernetes `Secret` each time a chart is installed, upgraded etc. These are of course useful in case you want to rollback, but they do pile up.
- **How to prune old helm chart revisions from a cluster**, when you're confident you no longer want to return to them?
- *(Just deleting the kubernetes secrets would work, but I suspect there's a more elegant way out there.)*
#1: Initial revision
Helm delete old releases
Helm keeps track of installed (and previous) releases by creating a kubernetes `Secret` each time a chart is installed, upgraded etc. These are of course useful in case you want to rollback, but they do pile up. **How to prune old helm chart releases from a cluster**, when you're confident you no longer want to return to them? *(Just deleting the kubernetes secrets would work, but I suspect there's a more elegant way out there.)*