technical accuracy pass: kubelet/runtime split, image vs container layer, exit 137 = SIGKILL, ArgoCD maps helm hooks, selfHeal/prune opt-in, scoped absolutes (reviewer findings)

2026-08-17 18:49:03 +10:00
parent fee0de72e6
commit e769007e0d
6 changed files with 78 additions and 51 deletions
@@ -24,10 +24,11 @@ every manifest calls, and `include`/`toYaml`/`default` compose them. The mental
 you are not writing YAML, you are writing a program whose OUTPUT is YAML - so render
 locally (`helm template`), read the output, and lint what came out, not what went in.
 Say it like you mean it: **review the render, not just the template.**
-FIELD NOTE (amber): ArgoCD deploys charts by running `helm template` - a pure render.
-Anything that needs a live cluster or an install lifecycle (`lookup`, hooks) is silently
-dead there. A chart that works under `helm install` can behave differently under GitOps -
-render the way your deployer renders.
+FIELD NOTE (amber, CORRECTED 2026-08-17): ArgoCD renders with `helm template` rather than
+running `helm install`, so the lifecycle differs. `lookup` comes back empty (no live cluster at
+render). Hooks are NOT dead: Argo maps Helm hooks onto its sync phases (pre-install/pre-upgrade
+-> PreSync, post-install/post-upgrade -> PostSync); rollback and test hooks have no equivalent.
+Render the way your deployer renders and check where hooks land.

 ## Move 2 - Contexts: the cluster's whole voice is one small file
 The fleet pattern: the chart owns EVERYTHING structural - resources, probes, security