Helm
Hard
Troubleshooting
During helm upgrade, which objects does Helm check for an invalid ownership metadata conflict?
Select your answer:
Show answer and explanation
Answer: Only objects added since the previous revision
Explanation
Helm diffs the stored manifest of the previous revision against the new one by kind and name. Only objects that are new in this revision go through the ownership check, which is why an upgrade that adds an existing ConfigMap to the chart fails with unable to continue with update. Objects already in the release are updated without the check.
More hard Helm questions
- 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?
- 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?