Reverse Engineering Cloud Native: Interoperability and Community
summary
Kubernetes becomes the de facto orchestrator and the ecosystem is driven by concrete interfaces: CNI (networking), CRI (runtime), CSI (storage) plus newer APIs like SMI and Cluster API. CNCF hosts 154 projects split into 95 sandbox, 37 incubation, 20 graduated; vendors use containerd (graduated) or CRI-O, gVisor and Firecracker provide runtimes, and Flannel Calico Cilium cover overlays and policies. Surveys show 98% report operational benefits, 76% pursue multi‑cloud and 92% run service mesh.
AI-written summary · about
chapters (8)
- 0:00Cloud Native interoperability
- 2:25Containers and Kubernetes
- 8:04CNI and CRI interoperability
- 13:00Extensibility with interfaces
- 17:17Sustainable communities
- 19:43Education for practitioners
- 21:49Impact on vendors and users
- 24:03Q&A on Kubernetes
related talks
25mReverse Engineering Cloud Native: Interoperability and Community
31mReverse Engineering Cloud Native: Interoperability and Community
14mKeynote: Reverse Engineering Cloud Native: Interoperability & Community
50mFlying through Cloud Native (CNCF)
23mMaking Cloud Native Computing Universal and Sustainable
08mKeynote: Kubernetes and Cloud Native: The Past, Present, and Future
30mContainers and Next Gen Infrastructure Ecosystem
33mCNCF TAG-Runtime: Cloud Native Open...