Helm
Hard
Troubleshooting
Why can a Helm 4 upgrade stopped with SIGKILL leave the release in pending-upgrade when Ctrl+C doesn't?
Select your answer:
Show answer and explanation
Answer: Helm traps SIGINT and SIGTERM to record failed; SIGKILL can't be trapped
Explanation
During an upgrade, Helm listens for SIGINT and SIGTERM, cancels the operation and records the revision as failed, which doesn't block later upgrades. SIGKILL ends the process at once, so the revision keeps its pending-upgrade status. That's why CI job timeouts should be longer than Helm's own --timeout.
More hard Helm questions
- 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?
- Which command can render templates but also show Kubernetes object diffs against the cluster when combined with other tools?