CSI in Kubernetes
summary
Kubernetes is moving storage out of the control plane into external CSI drivers so vendors ship containers that speak gRPC over a UNIX socket; legacy 22 in-tree plugins are being replaced (one in-tree plugin now delegates to CSI). Users keep PVCs; cluster admins must run sidecars like external-provisioner, external-attacher and node-driver-registrar (usually a DaemonSet for node-side, Deployment with leader election for controller-side), give them high pod priority, and watch PVC events and sidecar logs. Demo shows an AWS EBS volume created (volumeHandle like xvdB) and mounted by the node driver; CSI stays out of the data path. Topology and snapshots are in alpha (1.15/1.13 timeline) and migration requires deleting and recreating PVs as CSI volumes.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:07What is CSI
- 3:08How CSI started
- 5:24About CSI
- 10:29Users
- 12:40Installation
- 17:47External Teacher
- 22:53Driver Registrar
- 26:27Questions
- 29:31Mistakes
- 34:32Current status
- 39:22Current plan
related talks
32mUnderstanding Kubernetes Storage: Getting in Deep by Writing a CSI Driver
39mContainer Storage Interface: Present and Future
01h 27mIntro + Deep Dive: Kubernetes Storage SIG
27mCeph-CSI: The Engine Behind Persistent Storage in Kubernetes
01h 16mIntro + Deep Dive: Kubernetes Storage SIG
01h 24mTutorial: Introduction to Using the Container Storage Interface (CSI) Primitives
34mKubernetes SIG Storage Introduction and Update
27mKubernetes SIG Storage: Intro & Deep Dive