Secure Pods
summary
Defines a "secure pod" as a sandboxed pod that uses a separate guest kernel to add a second security boundary so kernel bugs like Dirty COW require a hypervisor exploit to escape. Describes implementations: Kata Containers (lightweight VMs) and gVisor (user‑space kernel), notes memory and visibility overheads, and details real risks: the subPath symlink CVE, logging parser bugs (fluentd), and cluster metadata leaks. Experimental runtime selection via cri‑o/containerd annotations exists now; target is alpha in 1.12.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:10Threats from the outside
- 2:49Why do we care?
- 4:00Attack Surfaces
- 5:03Attacks via the Kernel
- 5:56Today: kernel isolation features
- 9:28Sandboxes - Visor
- 14:25TODO: Sandboxed storage
- 16:37Attacks over the network
- 17:36Network Policy
- 18:09Attacks via system logs
- 20:36Attacks via the Hardware
- 23:20Get Involved!
related talks
26mSecure Containers Deployments: Time for Refresh
19mSandbox to confidential containers: A brief on the evolution of container isolation
29mLayers of Isolation in Kubernetes
47mContainer Security
35mThe Enemy Within: Running Untrusted Code with gVisor
35mThe Enemy Within: Running Untrusted Code with gVisor
23mSecurity in a containerized world
22mSandboxes all the way down - A hitchhiker's guide to platform...
