Russian Doll: Extending Containers with Nested Processes

on YouTube ↗31m

" summary

Kubernetes pods start all containers together, so the solution overrides each container’s entrypoint by injecting a statically linked Go binary into a shared volume and passing the original command to it, letting that binary run the step, write a file to signal the next step, and use a controller that annotates the pod when injected sidecars are ready (projected via the downward API). It requires fetching image entrypoint metadata from registries, produces ambiguous start timestamps, and can be replaced later by a supervising sidecar or native ordering.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 2:32Overview
3. 6:51Requirements
4. 8:57Knit Containers
5. 10:22Terrible Hacks
6. 15:17Demo
7. 25:03Dependency
8. 27:03Health checks
9. 28:15Deployment controller
10. 29:18Question

" related talks

• 30mComposition of containers - A design pattern for applications running on K8sRachit Arora · ContainerDays 2022
• 40mContainerizing Rails: Techniques, Pitfalls, & Best PracticesDaniel Azuma · RailsConf 2018
• 37mManaging Containers at Scale with CoreOS and KubernetesKelsey Hightower · Strange Loop 2015
• 29mGoing from containers, to pods, to Kubernetes – help for your dev environmentsCedric Clyburn · DevConf.US 2024
• 29mUnderstanding the Container RevolutionRobert Lemke · International PHP Conference Spring 2017
• 49mContainers without DockerBen Hall · NDC Minnesota 2018
• 53mManaging Containers at Scale with CoreOS and KubernetesKelsey Hightower · Philly ETE 2015
• 27mPragmatic Pod Patterns: Leveraging sidecar containers in KubernetesJames Relph · Container Camp UK 2018