Helm
Hard
Helm v4
In Helm 4, which wait strategy does helm upgrade use when you don't pass the --wait flag at all?
Select your answer:
Show answer and explanation
Answer: hookOnly
Explanation
Without --wait, Helm 4 uses the hookOnly strategy, which waits for hooks but not for the release's workloads to become ready. A bare --wait selects watcher, which follows resource status, and --wait=legacy keeps the Helm 3 behavior. --rollback-on-failure also turns on watcher.
More hard Helm questions
- A Helm release's only revision is stuck in pending-install. Which recovery works?
- Why can a Helm 4 upgrade stopped with SIGKILL leave the release in pending-upgrade when Ctrl+C doesn't?
- 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?