Kubernetes end users have trouble deploying multiple containers that write to the same persistent volume.
Kubernetes administrators lack native solutions for hard separation of shared storage across multiple tenants.
The new Manila CSI plugin for the OpenStack Cloud Provider enables solutions for both problems.
Kubernetes end-users can follow a simple design pattern to write safely to dynamically provisioned general purpose RWX volumes
Kubernetes administrators can deploy Manila CSI using a straight-forward set of manifests
Manila administrators can set up service for Manila CSI with a minimum of fuss
Cloud Provider OpenStack Keystone can be used for hard tenant separation without sacrificing the economies of shared scale out infrastructure and elastic self-service provisioning
Demos, yaml, and manila configuration included.
- Why storage for Kubernetes has been hard.
- Advantages of CSI plugin approach for Kubernetes
- What is the new Manila CSI plugin
- How Kubernetes Admins would deploy it
- How Kubernetes users could use it without knowing about it
- How Manila admins can support it
- Comparisons with other CSI plugins and non-CSI storage solutions for Kubernetes
- Tenancy models for Kubernetes and Openstack, including advantages of Cloud Provider Openstack and Manila CSI
