Don't Peek Into my Container!
summary
Describes a working stack that combines Kubernetes + cri-o + KVM to run encrypted containers: workload mode boots a VM per container using libkiran and an attestation server that returns an encrypted secret with the kernel cmdline and LUKS passphrase, while container mode runs pods inside Kata Containers VMs with image download and attestation inside the guest. Builds a single-layer encrypted OCI image (fake entrypoint) on a trusted builder, switches to virtio‑block with LUKS2 AEAD and a minimal firmware to keep measurements stable, and demonstrates end‑to‑end attestation and secret injection.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 6:29Confidential workloads with Kubernetes and Libkran
- 10:21AMD SEV changes
- 17:45Kata Containers approach
- 23:19Modifying components
- 30:39Future of confidential containers
related talks
01h 14mHands-on Workshop: Confidential Containers: Bringing Confid...
32mLotsa security - confining the extra security layer
26mConfidential Containers with the Crun-Krun Container Runtime
50mConfidential Containers: Why, How, and Where Are We?
27mTrust No One: Bringing Confidential Computing to Containers
23mKubernetes + Encrypted Memory = Security * Privacy
32mProtecting Sensitive Code with Encrypted Container Images on...
38mConfidential Containers Explained