The Art of GitOps: Rendered Manifests
summary
Advocates render Helm or Kustomize with CI (helm template / kustomize build) and commit the output into environment-specific branches so the repo stores the exact manifests the cluster will receive. This gives an immutable desired state, earlier failure detection in CI, and measurable performance gains for Argo CD/Flux by removing runtime rendering. Tradeoffs include added CI complexity, plaintext secret concerns with Sealed Secrets (use External Secrets), loss of some Helm controller features, and experimental tools like the cargo-render GitHub Action.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:35Config Management Tools
- 2:48The Problem
- 10:09The Advantages
- 15:18Cargo Render
- 16:44Hot Takes
- 18:28Outro
related talks
23mRendered Manifests and OCI
28mShip It Faster, Safer & Cheaper GitOps with Helm
29mHow to Preview and Diff Your Argo CD Deployments
25mGit Sh*t Done, the GitOps Way
23mGitOps: yea or nay?
09mLightning Talk: Best Practices on Organizing GitOps Repositories
26mGitOps: yea or nay?
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm