Third Party Dynamic Volume Provisioners
summary
Kubernetes 1.4/1.5 adds a protocol that lets an external provisioner daemon watch for PVCs with a storageClass annotation, call out to real storage, create a PV object, and later delete the backing asset. The reference implementation is an NFS provisioner skeleton in Go that runs as a pod, serves exports, and works for dev labs but stores data on one node (not production‑durable). Provisioners implement simple provision/delete hooks, must honor capacity/accessModes/selectors, and rely on Kubernetes to resolve races.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 0:45Storage in Kubernetes
- 1:56Storage in COBOL
- 4:16Dynamic Provisioning
- 4:53Cloud Volume Provisioning
- 5:30Dynamic Volume Provisioning
- 7:44Hardcoded provisions
- 8:03External dynamic provisioning
- 9:16New Annotation
- 11:43How it should work
- 14:20How it works
- 14:39External Provisional Coordinator
- 14:58Summary
- 15:21NFS Provisional
- 18:28Recommendation
- 18:59NFS
- 26:59What to Provision
- 29:20Race Conditions
- 32:10Other options
- 34:06NFS Provision Error
- 35:39Personal Volumes
- 37:39Snapshots
- 38:24Guarantee
- 39:08Dependencies
- 40:02Support Pack
- 41:11Secret Sauce
- 41:44Risk Schedule
- 42:52PBs
- 43:11NFS Provision
- 43:55Capabilities
- 44:14Userspace
related talks
28mKubernetes Storage Evolution: Enabling High Performance Distributed Datastores
24mCapacity-aware Dynamic Volume Provisioning For LVM-based Local Storage
37mKubernetes Storage 101
05mLightning Talk: Automate Local Volume Provisioning with Local-Volume-Provisioner
05mLightning Talk: Automate Local Volume Provisioning with Local-Volume-Provisioner
30mKubernetes Storage Cheat Sheet for VM Administrators
36mTips and tricks for Kubernetes storage
22mKeep Persistent Volumes Healthy for Stateful Workloads