Reverse Engineering Cloud Native: Interoperability and Community
summary
Reverse engineers cloud native growth into concrete cause and effect: interfaces (CNI/CRI/CSI/SMI/Cluster API) enable the ecosystem, not hype. Cites adoption metrics — 99% see Kubernetes benefits, 52% need bare metal, 88% run >6 clusters — and lists real interoperable pieces: containerd and CRI-O for runtimes, gVisor and Firecracker for vendor sandboxes, and kubevela Crossplane Backstage for developer UX. Notes graduated projects (Rook, Prometheus, Linkerd), CNCF exam/workshop outputs (KCNA, free Udacity course) as deliverables.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 0:44About Katie
- 1:36Agenda
- 3:08Kubernetes
- 3:26Container Primitives
- 4:24Challenges
- 5:28Container Orchestrators
- 6:10Kubernetes State
- 8:04Cloud Native Landscape
- 9:30Maturity of Cloud Native
- 10:37Networking
- 10:57Pods
- 11:43Networking Packet
- 13:20Container Network Interface
- 13:33Networking Tools
- 15:55Runtime Interface
- 16:08Interoperability Principles
- 16:55The Landscape
- 17:24Service Mesh Interface
- 20:41Application Deployment
- 22:29Open Governance
- 23:03CNCF
- 25:42Diversity
- 26:12Cloud Native and Data Science
- 28:18AI Data Foundation
- 29:01Open Source Community
- 30:05Apple Hiring
- 30:32Medium Blog Post
- 30:50Questions
- 31:14Feedback
related talks
31mReverse Engineering Cloud Native: Interoperability and Community
25mReverse Engineering Cloud Native: Interoperability and Community
22mOpen Standards: Anchoring Extensibility for Cloud-Native Tooling
50mFlying through Cloud Native (CNCF)
23mMaking Cloud Native Computing Universal and Sustainable
20mKeynote: What is Cloud Native and Why Should I Care?
22mThe Irresistible Rise of Cloud Native: What the Future Means for YOU
43m(Mis)Understanding Cloud-Native