GitOps and KRO: A New Way to Control Cloud Infra
summary
KRO (aka Crow) packages multiple Kubernetes manifests into a single resource graph definition and automatically creates CRDs and controllers to reconcile them server-side. Demo shows Argo CD plus GCP Config Connector creating a Cloud SQL instance, a bucket and a Deployment that receives DB IP and connection name — reconciliation completes successfully though cloud resources take time. KRO does server-side templating and validation, plays with Crossplane/Helm/Terraform, and is alpha — not for production.
AI-written summary · about
chapters (9)
- 0:00GitOps and KRO intro
- 4:17What is Cube Resource Orchestrator
- 7:10Why KRO matters
- 13:08How KRO works
- 17:20Cube Resource Orchestrator vs Crossplane
- 20:27Cube Resource Orchestrator with GitOps
- 23:41Live demo of KRO
- 32:00Future of Cube Resource Orchestrator
- 33:45Q&A
related talks
35mIntroducing Kubernetes Resource Orchestrator (KRO)
24mKubernetes-Powered Platform Engineering: From IaC To API-Driven Infrastructure
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes
39mGitOps — How to Marry Git and Kubernetes for Deployment and Operations
28mGitOps in Kubernetes
31mAutomating Kubernetes Resource Management Over GitOps for the Telco Cloud RAN Prime Time
34mGitOps for the Free Cloud: Bridging Kubernetes and OpenStack with ORC
35mPlays Well with Others: Composability for Cloud Native Applications