Panel: Expanding Argo CD Content Management Using OCI Artifacts
summary
Proposal converts an OCI registry into an Argo CD application source so CI pushes a packaged bundle (Helm charts or rendered manifests) into a registry and Argo pulls and deploys it using the oras library already in use. It highlights edge cases where Git is disallowed, shows OCI Helm GA and Flux parity, flags immutability issues with tags versus use digests not tags, and recommends signing/policy checks so registries become OCI registry as application source with oras library underneath.
AI-written summary · about
chapters (7)
- 0:00Introduction and panel
- 1:59Defining OCI artifacts
- 5:06The enhancement proposal
- 7:01Scaling and use cases
- 12:13Technical implementation
- 14:56Security and audience Q&A
- 22:06Closing remarks
related talks
23mRendered Manifests and OCI
36mModifying the Immutable: Attaching Artifacts to OCI Images
06mGit Going Fast with Cilium and Argo
10mLightning Talk: OCI Images for More Than Containers, Jon Johnson, Google
36mIt’s Complicated: Relationships Between Objects In OCI Registries
37mDeep-dive into Open Policy Agent + Conftest + GateKeeper
35mStore AI/ML models efficiently with OCI Artifacts
45mOCIv2: Container Images Considered Harmful