Sidecars at Netflix: From Basic Injection to First Class Ci...
summary
Netflix runs sidecars by packaging immutable system services into each container using rootless containers, a tiny init (tini) that creates namespaces and cgroups, systemd units to enforce startup and shutdown ordering, runC to launch processes, and a small injector for things like SSH and metadata interception. This executor model proves reliable (avoids pause containers, ties service lifetime to the app), but Kubernetes lacks ordering and user namespace features, prompting a pre-KEP effort and several orgs to maintain kubelet forks.
AI-written summary · about
chapters (5)
related talks
33mMagic of Kubernetes Sidecar Injection: Present and Future - Anton Ovchinnikov
29mThe Great Sidecar Debate
25mRelease the Kraken: Bring Sidecar Containers to Next Level
27mPragmatic Pod Patterns: Leveraging sidecar containers in Kubernetes
38mContainer Linux: The Next 10 Years
30mContainers and Next Gen Infrastructure Ecosystem
29mKube-Oddities - the quirks that keep Kubernetes interesting
27mProductionise any Application in Kubernetes Using Sidecar Containers