Alauda Persistent Container Storage
LINBIT® combined with the Alauda® Container Platform (ACP) delivers a future-ready hyper convergent cloud-native environment.
The production-grade persistent container storage for ACP Kubernetes works seamlessly with your most critical and intensive business applications.
Architecture
In ACP Kubernetes building, operating, and layering block storage becomes simple. The LINSTOR® Operator can be used to create highly available LINSTOR storage clusters in ACP Kubernetes – running on premise or in the cloud.
LINSTOR clusters are composed of controller and satellite nodes that connect to each other and to ACP Kubernetes over TLS secured connections. Interacting with the LINSTOR cluster can be done using the CLI, API, or using the LINSTOR GUI.
Benefits
- Uniformity Across Cloud & On-prem Platforms
- Highly Available Persistent Volumes
- Prometheus Monitoring Endpoint
- Snapshot Shipping and Scheduling
- Separation of Data & Control Plane
- Deduplication using VDO
- Encryption at Rest using LUKS
- Hardware and Cloud Agnosticism
- Topology Awareness for Latency Sensitive Databases
- Support for Most Major Linux Distributions
- Support for amd64 and arm64 CPU Architectures
Business Value
24 x 365
Support
No Vendor
Lock-In
Lower
TCO
Scale
Out
High
Performance
Open
Source
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.
