SMB CSI Driver gives Kubernetes access to SMB shares on Linux and Windows

⚡ The gist in 5 seconds - SMB CSI Driver connects an SMB server to Kubernetes from pods on both Linux and Windows nodes. - An already deployed and configured SMB server is required — the driver does not create the share itself. - Dynamic provisioning of persistent volumes (PV) via Persistent Volume Claims is supported. ### 🔍 What was found The SMB CSI Driver project is a Container Storage Interface driver that gives a Kubernetes cluster access to an SMB server. It is claimed to work on two types of nodes: Linux and Windows, meaning the driver is designed with mixed clusters in mind. The key requirement is that the SMB server must already exist and be configured in advance: the driver itself provides access to the storage rather than setting it up. The version number, supported Kubernetes releases, and other technical details are not provided in the source. The mechanics follow the standard Kubernetes scenario: a Persistent Volume Claim created in the cluster is dynamically turned into a persistent volume on the SMB share side. The driver implements the CSI interface, so it connects to the cluster as a regular CSI storage plugin, without manually mounting shares on each node. Cross-platform support is emphasized separately: the same driver serves both Linux and Windows nodes. ### 💡 Why it matters SMB/CIFS remains the primary protocol for corporate file storage, and Kubernetes clusters in such environments almost always have to be integrated with already running file servers. SMB CSI Driver addresses exactly this task, eliminating the need to mount shares manually, and does so uniformly for both Linux and Windows nodes. For administrators, this means persistent volumes for application state can be provisioned from existing SMB infrastructure through familiar PVCs, rather than through a separate storage layer.