Build and Deploy Cloud Native (OCI) Artifacts, the GitOps Way
summary
Packages Helm charts and Gatekeeper policies as OCI artifacts, stores them in GitHub Container Registry, and validates them in CI with Gator unit tests and Trivy scans before pushing via ORAS push/pull. Config Sync then deploys the OCI artifact and Kustomize/Helm manifests so the cluster sees constraints and templates; Gatekeeper enforces (demo shows zero violations) and CI blocks on policy failures. Claims OCI is more performant at scale because of Config Sync pulling OCI sources instead of many git clones.
AI-written summary · about
chapters (9)
- 0:00GitOps and OCI artifacts intro
- 2:30OCI artifacts and benefits
- 5:25Config Sync and controllers
- 7:17Gatekeeper security policies
- 8:00Demo setup overview
- 15:29Demo: Gatekeeper policies as OCI
- 16:10Demo: Helm charts as OCI
- 21:54Key takeaways
- 24:47Q&A
related talks
21mContinuous Delivery: The Missing Piece in the GitOps-OCI Security Puzzle
25mGit Sh*t Done, the GitOps Way
29mThe Evolution of GitOps in Platform Engineering
30mGitOps: Keeping It Light, Bright, and Deployed Right with OpenShift!
30mOrganizing Teams for GitOps and Cloud Native Deployments
19mCross Domain DevSecOps with GitLab and Oracle Cloud
40mHow GitOps Changes Everything in CI/CD
20mMulti-Stage Deployment Pipelines the GitOps Way