// the take
An operator that runs LINSTOR/DRBD-based replicated block storage on Kubernetes, giving you a CSI driver backed by synchronously-replicated volumes across nodes instead of relying on a SAN or cloud disk. It's for teams running on bare metal or VMs who want local-disk performance with replication, and are willing to deal with a kernel module to get it.
The CRD design is genuinely granular — LinstorCluster, LinstorSatellite, LinstorNodeConnection and LinstorSatelliteConfiguration let you tune cluster-wide defaults, per-node overrides, and node-to-node link config separately instead of one monolithic spec. It ships a CSI driver, an HA controller for failover, and an affinity controller, so the common operational pieces aren't left as DIY. TLS is handled either via cert-manager or a bundled gencert fallback, which is a reasonable answer for clusters that don't run cert-manager. Docs follow an actual tutorial/how-to/reference/explanation split with per-distro guides (k0s, Talos, OpenShift, microk8s, Flatcar), which is more thought-through than most operators at this star count.
DRBD needs a kernel module, so node compatibility is a real constraint — the secure-boot MOK enrollment doc and the separate kernel-headers how-to exist because this bites people on locked-down or minimal-image nodes, and it rules out most managed Kubernetes offerings outright. V1 to V2 has no automated migration path; the docs walk through a multi-step manual process (collect v1 info, remove v1, install v2, migrate the database) rather than an in-place upgrade. The project is effectively single-vendor (LINBIT) with LINSTOR itself as closed-ish upstream tooling the operator wraps, so community contribution outside the vendor is thin despite 80 forks. At 564 stars this has nowhere near the production mileage of Rook/Ceph or OpenEBS, so expect to hit edge cases in storage-pool handling or satellite probing (both have dedicated test files, suggesting they've already been a source of bugs) that a bigger user base would have already surfaced.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →