Helm
Hard
Concepts
You re-annotate ConfigMap flags so release 'platform' owns it, then upgrade release 'web' with a chart that no longer renders it. What happens to flags?
Select your answer:
Show answer and explanation
Answer: Helm deletes it unless it has helm.sh/resource-policy: keep
Explanation
On upgrade, Helm deletes objects that were in the previous manifest but not in the new one, and the only thing it checks on the live object first is the helm.sh/resource-policy: keep annotation. It doesn't check who owns the object now. The ownership check before deleting was added to helm uninstall in 4.3, not to upgrade.
More hard Helm questions
- helm install --dry-run=server fails with invalid ownership metadata for one Deployment. What does this tell you about the chart's other existing objects?
- What is the purpose of the 'helm verify' command?
- What is the purpose of the 'helm get hooks' command?
- Which Helm capability provides cluster information like API versions available?
- Which annotation is commonly used to mark a resource as a Helm hook?
- Which manifest hook weight determines order when multiple hooks of the same type run?