Production-Ready Platform Engineering: Build To FAIL
summary
Argues that Kubernetes’ extendable API becomes the control plane for everything: uses Cluster API to provision clusters, Crossplane to create cloud resources (S3, VNet) from YAML, and KubeVirt to run full VMs from uploaded ISOs as Kubernetes objects; shows manifest snippets, Azure auth flows, and a button-click IDP (Port) tied to pipelines; claims 50+ OIDC providers force generalists, predicts the Kubernetes-era API model lasts ~5–7 years and infrastructure should be ephemeral like containers.
AI-written summary · about
chapters (9)
- 0:00Introduction and Speaker Background
- 0:37Understanding Distributed Systems
- 1:04Challenges in Modern Infrastructure
- 3:34The Evolution of Platform Engineering
- 4:36Kubernetes and Its Future
- 6:19Building a Modern Tech Stack
- 13:20Developer Experience and Internal Developer Platforms
- 16:07Practical Demonstrations and Tools
- 18:22Conclusion and Final Thoughts
related talks
43mPlatform Engineering Redefined: Evolving Kubernetes Beyond Container Orchestration
20mWhat Does A Platform On Kubernetes Look Like?
07mBuilding Kubernetes-native applications
18mThe Past, the Present, and the Future of Platform Engineering
40mThe Elephant in the Kubernetes Room: Team Interactions
41mArchitecting Kubernetes-Based Internal Developer Platforms: Essential Patterns...
31mThe 20 Year Platform – bringing together Kubernetes, 12-Factor and Functions
24mKubernetes-Powered Platform Engineering: From IaC To API-Driven Infrastructure