Estimate total execution time added by pre/post-install and upgrade Helm hooks.
Helm hooks of the same type (e.g. all `pre-upgrade` hooks) execute in ascending `helm.sh/hook-weight` order, and Helm waits for each weighted group to complete before moving to the next — so total hook time for a given phase is the sum of each hook's duration in weight order, not the maximum. This is why chaining many sequential hooks (migrations, cache warms, smoke tests) can add up to a meaningful share of total upgrade time even when no single hook is individually slow.
totalTime = hook1Duration + hook2Duration + hook3Duration (sequential)
`helm.sh/hook-weight` is an annotation (string-encoded integer, can be negative) that determines execution order within the same hook type — lower weights run first, and Helm waits for each to reach a successful state before starting the next.
No — Helm executes hooks of the same type strictly in ascending weight order, one at a time; only hooks that share the exact same weight value have no defined ordering guarantee relative to each other, though Helm still doesn't guarantee true concurrent execution of those either.
By default Helm aborts the operation on hook failure (unless `helm.sh/hook-delete-policy` and error handling dictate otherwise), so a slow or failing early-weight hook blocks all subsequent hooks and the rest of the upgrade from proceeding.