Rendered Manifests and OCI
summary
The rendered manifests pattern moves templating into CI so Helm/Kustomize output becomes an immutable artifact (stored in environment deployment branches or pushed to an OCI registry via ORAS) and Argo CD v3.1+ consumes raw YAML directly. This gives rendered manifests pattern visibility and immutability, enables air‑gapped/edge use, and removes implied Git/Helm runtime dependencies, but it shifts complexity to CI, makes diffs harder, and renders sealed secrets as plaintext unless replaced with an external secrets operator.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:48Desired state in Kubernetes
- 3:55Argo CD and raw YAML
- 6:44Rendered manifest pattern
- 8:33GitOps with environment branches
- 10:18Advantages and disadvantages of rendered manifests
- 12:08What is OCI
- 14:58OCI registries with ORAS
- 16:44Argo CD and Helm OCI support
- 18:31Why OCI matters for Argo CD
- 19:55Rendered manifests with OCI
- 21:01OCI-based GitOps pros and challenges
related talks
19mThe Art of GitOps: Rendered Manifests
29mHow to Preview and Diff Your Argo CD Deployments
09mThe thin line between code and configuration (YAML/Helm rant)
23mPanel: Expanding Argo CD Content Management Using OCI Artifacts
26mAre We Stuck With Helm Forever? A Landscape of Cloud Native CNF Manag...
31mBuild and Deploy Cloud Native (OCI) Artifacts, the GitOps Way
23mTales from the Crypt: Application Packaging and Delivery Nightmares
27mThere's No Place Like Production