Helm release status and CI/CD log correlation for post‑install hook failures

Determine whether a failing post‑install hook changes the Helm release status reported by helm status and whether that change is observable in the CI/CD pipeline logs without enabling additional debugging.

In Helm v3 each release is persisted as a Secret, and hook execution logs are written to the hook’s pod rather than to the release resource. The CI system typically captures the helm command’s stdout and stderr, but hook output appears only if the pod logs are collected separately. It is unclear whether Helm automatically marks the release as FAILED when a hook errors, leaving the status as DEPLOYED while the failure is visible only in hook logs.

Does Helm automatically set the release status to FAILED when a post‑install hook returns a non‑zero exit code? If the status stays DEPLOYED, what specific log lines in the CI output indicate the hook failure? Can the CI pipeline rely on helm status alone to judge deployment success, or must it also inspect hook logs?