OCI Is Not Git: Rethinking the GitOps Source of Truth for a Kubernetes-Native…
summary
Kokumi is an experimental Kubernetes operator that renders Helm and Kustomize input into OCI artifacts, pushes them to a registry (optionally an in-cluster registry), and creates an Argo CD Application pointing at the produced digest so clusters pull immutable revisions. It exposes Order / Preparation / Serving CRDs to record builds and promotion, offers a UI for diffing and promoting rendered manifests, and targets edge and air-gapped distribution bundle workflows; it currently lacks full SCM-style blame, PR discussion, and some enterprise auth/webhook integrations, but 1.14 adds login and private registry support.
AI-written summary · about
chapters (10)
- 0:00GitOps and OCI skepticism
- 3:52Why OCI skepticism matters
- 6:39OCI features for GitOps
- 8:49GitOps vs OCI workflows
- 11:35OCI limitations vs Git
- 14:27Kuku me for OCI GitOps
- 17:39Live demo of Kuku me
- 22:15What Kuku me solves
- 23:57Future of OCI and GitOps
- 24:59Q&A
related talks
39mGitOps — How to Marry Git and Kubernetes for Deployment and Operations
45mGitops: The Kubernetes way
30mManage your kubernetes cluster in the GITOPS way !!
25mGit Sh*t Done, the GitOps Way
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes
30mGitOps: Keeping It Light, Bright, and Deployed Right with OpenShift!
38mGitOps x Kubernetes: Argo CD gives us the winning combo
02h 38mStop using kubectl, and use Git instead! - Hands-on GitOps workshop using Argo CD and Helm