The Cloud Provider OpenStack repository is a Kubernetes integration project written in Go that hosts multiple plugins enabling seamless interaction between OpenStack infrastructure and Kubernetes clusters. The repository serves as a central hub for cloud provider functionality, storage solutions, authentication mechanisms, and load balancing capabilities tailored specifically for OpenStack environments.
The repository contains eight major components addressing different aspects of Kubernetes-OpenStack integration. The OpenStack Cloud Controller Manager provides core cloud provider functionality for managing nodes, load balancers, and routes within OpenStack. The Octavia Ingress Controller handles ingress traffic management using OpenStack's Octavia load balancing service. For persistent storage, the repository includes both the Cinder CSI Plugin for block storage and the Manila CSI Plugin for shared file storage, replacing earlier provisioner implementations that were deprecated in version 1.18.0. Authentication and authorization are handled through Keystone Webhook Authentication Authorization and Client Keystone Auth, integrating OpenStack's identity service with Kubernetes. The Barbican KMS Plugin provides encryption key management through OpenStack's key management service, while the Magnum Auto Healer addresses cluster health management for Magnum-deployed clusters.
The project has undergone significant evolution, with notable deprecations reflecting changing Kubernetes storage patterns. The Cinder Standalone Provisioner, Manila Provisioner, and Cinder FlexVolume Driver were removed starting with version 1.18.0, with version 1.17 being the final release supporting the Manila Provisioner. Additionally, beginning with release 1.26.0, support for the older Neutron LBaaSv1 load balancing was removed, with Octavia becoming the sole supported load balancing backend.
Activity tracking reveals an engaged but distributed contributor base.
This interconnection indicates the project's importance within the broader Kubernetes ecosystem and its relevance to multiple deployment scenarios. The project maintains active community engagement through the Kubernetes provider-openstack Slack channel, with four designated project co-leads coordinating development efforts.
