Kubernetes as a Platform Framework Journey from IaC Pipelines to K8s APIs
summary
Argues platform bottlenecks are not CI/CD but external cloud resources, claiming orgs still take 6–12 months to ship features because of ticket‑ops and thousands of apps. Shows a working demo using Argo CD, ACK (AWS Controllers for Kubernetes), Crossplane and Gatekeeper: an Argo sync‑wave creates an S3 bucket plus IAM role/policy created, an external job pulls the ARN into a secret and the app uploads test.txt. Notes 46 ACK controllers GA today and recommends treating Kubernetes APIs as the platform API to eliminate manual tickets.
AI-written summary · about
chapters (6)
- 0:00Platform engineering challenges
- 4:41Two decades of automation inefficiencies
- 15:52Bottlenecks solved with K8s APIs
- 21:59Crossplane and ACK AWS demo
- 27:41CNCF tools integration and outlook
- 31:45Platform frameworks evolution
related talks
24mKubernetes-Powered Platform Engineering: From IaC To API-Driven Infrastructure
06mArgo CD and Kubernetes from event based to microservices
15mKubernetes Deployment from Platform to API
36mHow to Build Cloud-Native Platforms with Kubernetes
30mManage your kubernetes cluster in the GITOPS way !!
31mLearnings From Providing A Platform API With Kubernetes And Crossplane
35mDriving the Platform at Deutsche Bahn with Crossplanes Provider-Argocd
52mCloud-Native Kubernetes Workflows on AKS with Argo