The Rendered Manifests Pattern: Reveal Your True Desired State
summary
GitOps stores the rendered Kubernetes manifests, not the Helm or Kustomize charts; render those manifests in CI for main and write them to environment branches so Argo CD applies plain YAML directly. Uses Helm, Kustomize for rendering, Argo CD for reconciliation and cargo render as an example renderer. Benefits: diffs and linting before merge, avoids tool-version surprises, removes repeated runtime rendering (repo server RAM can reach ~200 GB), and shortens a 24-hour cache feedback loop. Downsides: CI picks up the rendering complexity and cargo render is pre‑alpha.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:15The Rendered Manifest Pattern
- 3:25The Risks
- 11:47The Solution
- 15:46Demo
- 21:33Advantages
- 24:40Disadvantages
related talks
31mParadox Of Choice: How To Pick an Application Definition That Works For You!
27mLightning Talk: GitOps, A Slightly Realistic Situation on Kubernetes with Flux
06mArgo CD and Kubernetes from event based to microservices
28mDriving Monorepo Adoption With Backstage
33mLevel Up Your Developer Experience 🧭
27mDeveloper Platform Consoles Should Be Dumb
18mKeynote: Choose Your Own Adventure: The Perilous Passage to Production
18mMulti-environment deployment for K8s-based microservice arch