Improving Container Image Registry Availability with Kube Image Keeper
Talkat ContainerCon @ OSS EU 2023 · on Tuesday, 2023-09-19· at 12:20· Room 0A (Floor 0), Abandoibarra Etorb., 4, 48011 Bilbao, Bizkaia, Spain·
summary
Kube Image Keeper (kuik) implements a local registry cache plus a node-side proxy: a mutating webhook rewrites image refs to localhost:7439, a daemonset proxy serves cached blobs and falls back to upstream, and a controller populates a registry and CRD entries with reference counts; first pulls are duplicated, retention is ~30 days, and new nodes see a ~10–20s proxy startup delay. High availability uses MinIO-backed HA (S3-compatible object store). Operator is built with kubebuilder (easy CRD generation, painful upgrades).
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 2:58The problem of outages
- 7:46Installing the project
- 12:14How Quick works
- 20:57Comparing alternatives
- 26:54High availability demo
- 29:41Introduction to Kubebuilder
- 33:48Advanced demo and testing
- 42:23Q&A session
related talks
48mImproving Container Image Registry Availability with Kube Image Keeper
35mThe Growing Need for Caching Container Images in Kubernetes
37mCache Me If You Can: P2P Image Sharing in Kubernetes with Spegel
28mThe ABC of Container-Image Management
30mEstablishing Image Provenance and Security in Kubernetes - Adrian Mouat, Container Solutions
31mImage Provenance and Security in Kubernetes
28mKubernetes Multitenancy in Image Pulling
39mKubernetes and Checkpoint/Restore