Is a native, automated StorageClass workflow for Ceph directly supported on Windows containers today?
We have successfully built an operational Ceph storage cluster on Linux. Within our Kubernetes environment, we configured a standard Ceph StorageClass that allows our Linux pods and containers to dynamically provision, mount, and access this persistent storage seamlessly.
We are now looking to achieve the exact same user and developer experience for our Windows containers.
During our initial implementation steps, we ran into an issue finding stable, upstream Windows container images for the ceph-csi node driver. To work around this, we manually installed windows ceph msi and the Dokan file system driver directly onto our underlying Windows worker host nodes. Using this host-level setup, we can successfully mount the Ceph filesystem and verify that our cluster files are visible from the Windows host OS layer.
However, our ultimate goal is to consume this storage natively using a standard Kubernetes StorageClass and PersistentVolumeClaim (PVC) inside standard Windows containers, mirroring our native Linux workflow.
We would appreciate your help and insight on the following points:
Is a native, automated StorageClass workflow for Ceph directly supported on Windows containers today?
If it is supported, could you guide us on how to correctly configure the CSI layer or point us toward verified Windows-compatible node plugin images?
If a direct StorageClass approach is not supported due to platform limitations, what are the best-practice architectures or workarounds to bridge this gap effectively for production workloads?
