Containers and Next Gen Infrastructure Ecosystem
summary
Enterprise teams still lack a container strategy while the ecosystem consolidates: runtimes are moving to runc runtime and CRI implementations like containerd and cri-o, orchestration is settling on Kubernetes orchestration, and Docker exists as Moby/CE/EE confusion. Service meshes (notably Istio+Envoy service mesh) use sidecar proxies for layer‑7 control/data planes. The biggest bet is API extensibility — CRDs and custom controllers (kubebuilder/operator frameworks) enable millisecond event loops for stateful ops and island‑scale automation.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:57Johns books
- 2:35Spoiler alert
- 3:34Container Ecosystem
- 6:26Technology Based Future
- 7:23The Wild West
- 7:43The OCI
- 8:52The Container Ecosystem
- 9:08Three Categories
- 10:02Railcar
- 10:29Engine
- 12:36What is Docker
- 13:08Cloudbased container engines
- 13:38Kubernetes
- 14:26Kubernetes orchestration
- 18:34Service Smash
- 18:52Service Mesh
- 19:53Service Mesh Capabilities
- 20:39Service Mesh Architecture
- 22:23Pilot Mixer
- 24:49What was my idea
- 25:50Joseph Jackson
- 28:16Google Scale
- 28:49Stateful
- 29:24Coop Builder
- 29:45First Order Driver
related talks
39mThe future of infrastructure will be containerized
31mReverse Engineering Cloud Native: Interoperability and Community
25mContainers as an enabler for microservices and what it means for our industry
29mUnderstanding the Container Revolution
23mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes - Phil Estes, IBM
25mReverse Engineering Cloud Native: Interoperability and Community
37mLet's Try All the CRI Runtimes: Part 2: Answering the Why Question!
24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes