Helm upgrades finish setup updates
A release that adds a frozen Kubernetes object, such as a service account, used to stop a Helm deployment with no way forward. Now the customer's admin upgrades the chart, and the update finishes:
helm upgrade <release> <chart> --version <version> -n <namespace> --reset-then-reuse-valuesThe deployment page shows that command with the release name, namespace, and chart version filled in. Argo CD, Flux, and Terraform work the same way: set the chart version and apply as usual.
The upgraded chart tells Alien which setup it carries. Alien accepts it only when the chart matches the waiting release and the change stays inside Kubernetes objects the chart creates.
- Cloud resources: a release that also needs a new bucket or permission asks for the cloud part of initial setup first
- Older Helm:
--reset-then-reuse-valuesneeds Helm 3.14 or later. The page also shows the two commands for older versions - Declined charts:
helm upgradestill succeeds, the current release keeps running, and the page says why