Kubernetes Persistent Container Storage

LINBIT® builds upon 20 years of experience developing and supporting production storage and high availability workloads, combined with modern best practices from the community. 

Our production-grade software defined storage solutions combined with our world-class support for persistent container storage for Kubernetes works seamlessly with your most critical and intensive business applications.


With native integration to Kubernetes, LINSTOR® makes building, operating, and layering block storage simple. The LINSTOR Operator can be used to create highly available LINSTOR storage clusters in Kubernetes using Kubernetes native tools. It’s used to provide persistent block storage for Kubernetes environments running on premise or in the cloud.


LINSTOR clusters are composed of controller and satellite nodes that connect to each other and to Kubernetes over TLS secured connections. Interacting with the LINSTOR cluster can be done using the CLI, API, or using the LINSTOR GUI.


Business Value

24 x 365
No Vendor

Technical FAQ

Can LINBIT SDS be deployed in an "air-gapped" data center?

Yes. LINBIT SDS typically requires a connection to LINBIT's container registry (drbd.io). However, LINBIT's container images can be pulled into a local registry that can then be specified in the LINSTOR Operator's deployment manifest.

Does LINBIT SDS support third party Kubernetes backup solutions?

Yes.  Trilio, Bacula, Kasten, and Velero have been tested, but any CSI compliant backup solution should work since LINBIT SDS (LINSTOR) is CSI compliant.

What volume access modes does LINBIT SDS support?

LINBIT SDS supports the ReadWriteOnce (RWO) access mode. It is possible to use an NFS pod with a LINBIT SDS volume to “re-export” it with ReadWriteMany (RWX) access, but it is not directly supported by LINBIT SDS and therefore requires additional steps from the user.

For subscription and pricing details: