The kubernetes/cloud-provider-openstack project published release openstack-cinder-csi-2.36.5 on September 8 2026. This patch update delivers maintenance packaging for the OpenStack Cinder Container Storage Interface Helm chart. Operators running Kubernetes clusters on OpenStack infrastructure use this chart to deploy and manage block storage components.
The full release notes and downloads are on the GitHub release page.
OpenStack Cinder CSI Chart Release Packaging ¶
The openstack-cinder-csi-2.36.5 tag marks a patch release for the OpenStack Cinder Container Storage Interface Helm chart maintained within the kubernetes/cloud-provider-openstack repository. Helm charts for cloud provider storage drivers package controller deployments, node plugin daemonsets, service accounts, custom resource definitions, and RBAC rules into structured deployment templates. Patch releases in this release stream keep chart definitions aligned with driver updates, dependency versions, and image tags across OpenStack environments.
Decoupling storage driver deployment from core Kubernetes components allows platform teams to manage storage infrastructure out of tree. The openstack-cinder-csi chart deploys the driver controller as a deployment with leader election enabled for high availability across control plane nodes. Simultaneously, the chart deploys the node plugin as a daemonset across worker nodes to handle local block device attachments and filesystem formatting operations. Maintaining tagged chart releases enables platform engineering teams to track and deploy storage infrastructure changes via automated GitOps pipelines.
Storage Component Architecture and Controller Operations ¶
The OpenStack Cinder Container Storage Interface driver acts as the translation layer between Kubernetes volume management APIs and OpenStack block storage services. The controller plugin registers against the Kubernetes API server to monitor persistent volume claims and volume lifecycle events. When a stateful workload requests storage, the controller communicates with OpenStack Nova and Cinder API endpoints to provision block volumes, manage snapshots, and handle volume expansion.
Chart manifests configure essential driver options, including cloud configuration credentials, region selectors, availability zone topology rules, and API timeout parameters. Configuring these options through Helm values files provides explicit control over how the driver interacts with OpenStack Keystone authentication services. Pinned chart releases prevent unintended configuration drift when rolling out infrastructure updates across multiple cluster environments.
Node Plugin Deployment and Volume Attachment Mechanics ¶
The node plugin component runs on each Kubernetes worker node to execute low level storage tasks required by running pod containers. Once the controller attaches a Cinder volume to an OpenStack virtual machine instance, the local node plugin detects the block device, creates filesystem structures, and mounts the device into the target container directory.
Because the node daemonset maintains direct interactions with host operating system block devices and node kubelet sockets, updating chart templates requires careful validation. The Helm chart defines node plugin volume mounts, host path bindings, privileged security contexts, and driver registrar sidecar containers. Platform engineers must ensure that chart upgrades preserve existing volume mounts without interrupting active workload storage IO operations.
Operational Upgrade Best Practices for Storage Infrastructure ¶
Upgrading storage driver Helm charts in production environments requires validating rollout strategies for both controller deployments and node daemonsets. Operators should review chart values files prior to deployment to verify that custom volume parameters, storage class names, and secret references remain intact across release updates.
Using explicitly tagged releases like openstack-cinder-csi-2.36.5 ensures reproducible cluster provisioning across staging and production environments. Maintaining tag parity between chart releases and container image tags prevents operational mismatches between controller logic and template specifications. SRE teams should test chart upgrades in non production clusters to verify API communication with OpenStack infrastructure before updating production storage controllers.
Where to get it ¶
- Release page: GitHub release page
- Code repository:
kubernetes/cloud-provider-openstack - Release tag:
openstack-cinder-csi-2.36.5