The Growing Need for Caching Container Images in Kubernetes
summary
Caches container images inside the cluster using an image cache CRD and controller called kube-fledged, supporting Docker, containerd and cri-o and installable via YAML, Helm or Operator. It creates Kubernetes Jobs that delegate pulls to the kubelet, supports private registries with image pull secrets, and offers automatic or on‑demand refresh and node-subset placement. Prebuilt images on Docker Hub are whitelisted to avoid rate limits. Roadmap items include building caches from pod annotations, single‑pull distribution and image adoption for cluster-wide management.
AI-written summary · about
chapters (8)
- 0:00Introduction and agenda
- 2:58Use cases for image caching
- 6:48Introduction to Cube-fledged
- 11:03Technical architecture
- 16:09Resources and documentation
- 18:49Roadmap and future features
- 23:37Alternative solutions
- 28:25Q&A and closing remarks
related talks
48mImproving Container Image Registry Availability with Kube Image Keeper- 48mImproving Container Image Registry Availability with Kube Image Keeper
37mCache Me If You Can: P2P Image Sharing in Kubernetes with Spegel
25mRunning Cache-Efficient Builds at Scale on Kubernetes with BuildKit
40mNode-Level Optimization in Large Cluster Powered by Containerd Plugin
15mOptimizing Cache Usage in Docker Builds
26mContainerization crossroads: Experiences-Experiments-Expectations
25mBlazing-Fast Container Deployments: Image Caching With Block Storage