Providing Containerized Cinder Services to Baremetal Kubernetes Clusters [I]
summary
Claims that a containerized Cinder can run from the cinder repo via make + docker-compose and act as a standalone block service for bare‑metal Kubernetes, exposing real connection info (iSCSI, Ceph RBD, Fibre Channel not yet) through an external provisioner that calls cinder create/reserve/initialize_connection. Over 70 storage drivers and CI tests back the approach; dynamic provisioning, attach/detach and resize (K8s 1.9) are shown working, snapshots remain out‑of‑tree.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:27Introductions
- 2:09What is Cinder
- 3:54Cinder Demos
- 5:37Make
- 6:38Storage
- 9:04Volumes
- 10:35Connections
- 12:42Provisioner
- 14:33Attachments
- 16:54Equipment
- 19:05SISI Driver
- 20:11Continuous Integration Testing
- 21:32Wrap Up
related talks
25mConnecting ecosystems: How Cinder CSI, Ember CSI & Manila CSI leverage OpenStack bits in Kubernetes
01h 24mTutorial: Introduction to Using the Container Storage Interface (CSI) Primitives
40mCeph CSI Driver: Bridging Containers and Ceph
19mKeynote: Debunking the Myth: Kubernetes Storage is Hard
29mSuccess of CRI: Bringing Hypervisor Based Container to Kubernetes [I]
44mContainer Management at Scale
08mGold Sponsor Lightning Talk: The Future of Container Storage: CSI and Cloud Foundry
32mUnderstanding Kubernetes Storage: Getting in Deep by Writing a CSI Driver