# LINSTOR Operator 2.10.0 **URL:** \ **Category:** Release Announcements\ **Tags:** kubernetes, drbd\ **Created:** [November 5, 2025, 3:18pm UTC](https://forums.linbit.com/t/linstor-operator-2-10-0/1044 "2025-11-05T15:18:06Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![wanzenbug](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/wanzenbug/32/39_2.png) [@wanzenbug](https://forums.linbit.com/u/wanzenbug)\ **Post date:** [November 5, 2025, 3:18pm UTC](https://forums.linbit.com/t/linstor-operator-2-10-0/1044/1 "2025-11-05T15:18:06Z")
We've recently released version 2.10.0 of our Kubernetes Operator. This is the biggest release since the original Operator v2 back in 2023! Version v2.10.0 brings long awaited support for ReadWriteMany (RWX) volumes, along with Volume Group Snapshot support, integrations for Cluster API and more. First, RWX support is finally here. In order to use it after upgrading to v2.10.0, create a new PersistentVolumeClaim with "ReadWriteMany" access mode. Internally, this will spawn a new NFS server process, managed and made highly available using DRBD Reactor. Since we use DRBD Reactor, the volume needs to be configured for quorum (or fencing), so generally, 2 replicas are required. In addition, since NFS is used, do not expect the matching performance compared to ReadWriteOnce volumes. There are some things we expect to not fully work with RWX volumes, notably restoring a snapshot of such a volume. We are working on lifting this limitation, but we feel like the new feature already provides enough value to release right now. Secondly, we now support the Volume Group Snapshot[1] feature. This allows you to take consistent snapshots of multiple volumes, even when they are not used on the same nodes. Thirdly, we now integrate with the Machine Deletion Process[2] of Cluster API. This ensures clean node evacuation while performing rolling updates, letting one node drain, ensuring data is fully moved off the node before deletion. This requires deployment of the LINSTOR Affinity Controller, which is now deployed automatically by the Operator. If you previously used to install it via the Helm Chart, please remove the Helm release. Lastly, we improved the status output of various "kubectl" commands when viewing operator resources such as "LinstorCluster" and "LinstorSatelliteConfiguration". To upgrade, either point your kustomization.yaml at the new manifest:   [https://charts.linstor.io/static/v2.10.0.yaml](https://charts.linstor.io/static/v2.10.0.yaml) Or, if using helm, upgrade the linstor-operator chart:   helm repo update   helm upgrade linstor-operator linstor/linstor-operator --wait To get specific instructions to apply the update, check our users guide[3]. If you need to upgrade from Operator v1, check out our upgrade guide[4]. Source code is, as always, available upstream[5]. Best regards, Moritz [1]: [Kubernetes 1.32: Moving Volume Group Snapshots to Beta | Kubernetes](https://kubernetes.io/blog/2024/12/18/kubernetes-1-32-volume-group-snapshot-beta/) [2]: [Machine deletion process - The Cluster API Book](https://cluster-api.sigs.k8s.io/tasks/automated-machine-management/machine_deletions) [3]: [LINSTOR 1.0 en - LINBIT](https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-upgrade) [4]: [Migrating to Operator V2](https://charts.linstor.io/migration/) [5]: [GitHub - piraeusdatastore/piraeus-operator: The Piraeus Operator manages LINSTOR clusters in Kubernetes.](https://github.com/piraeusdatastore/piraeus-operator) Operator v2.10.0 Changelog ------------------------------------- ### Added - Deploy LINSTOR Affinity Controller as part of LINBIT SDS. - Add option to set replica count for Deployment components. - Integration with ClusterAPI to enable graceful node evacuation in case of rolling machine updates. - Additional status information on `LinstorCluster`, `LinstorSatelliteConfiguration` and `LinstorSatellite` resources. - Support for Volume Group Snapshots - Support for RWX file systems using regular LINSTOR CSI volumes. ### Changed - Set `shareProcessNamespace: true` on workloads to automatically reap orphaned processes. - LINSTOR CSI now uses `hostNetwork: true` so RWX mounts use a stable IP when connecting to NFS. - Updated images:     \* LINSTOR 1.32.3     \* LINSTOR CSI 1.10.1     \* DRBD Reactor 1.10.0     \* DRBD Shutdown Guard: 1.1.1     \* LINSTOR HA Controller 1.3.1     \* Latest CSI sidecars ---
**Author:** ![michael](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/michael/32/16_2.png) [@michael](https://forums.linbit.com/u/michael)\ **Post date:** [November 7, 2025, 1:53pm UTC](https://forums.linbit.com/t/linstor-operator-2-10-0/1044/2 "2025-11-07T13:53:57Z")
This LINBIT blog article, [Creating ReadWriteMany Persistent Volumes in Kubernetes by using LINSTOR](https://linbit.com/blog/creating-readwritemany-persistent-volumes-in-kubernetes-by-using-linstor/), explores the LINSTOR RWX volumes access feature in detail and shows how to configure RWX access for PersistentVolumes. ---
**Author:** ![kreeuwijk](https://avatars.discourse-cdn.com/v4/letter/k/7ea924/32.png) [@kreeuwijk](https://forums.linbit.com/u/kreeuwijk)\ **Post date:** [November 11, 2025, 10:30am UTC](https://forums.linbit.com/t/linstor-operator-2-10-0/1044/3 "2025-11-11T10:30:42Z")
What does this mean for Kubevirt support? Will a PVC of `mode: Block` that is RWX still use the two-primary option designed for Kubevirt? ---
**Author:** ![wanzenbug](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/wanzenbug/32/39_2.png) [@wanzenbug](https://forums.linbit.com/u/wanzenbug)\ **Post date:** [November 11, 2025, 12:43pm UTC](https://forums.linbit.com/t/linstor-operator-2-10-0/1044/4 "2025-11-11T12:43:10Z")
Yes, block volume mode remains unchanged. We anticipate the number of people using kubevirt to be much larger than users that need actual RWX for block volumes. ---
**Author:** ![kreeuwijk](https://avatars.discourse-cdn.com/v4/letter/k/7ea924/32.png) [@kreeuwijk](https://forums.linbit.com/u/kreeuwijk)\ **Post date:** [November 11, 2025, 2:52pm UTC](https://forums.linbit.com/t/linstor-operator-2-10-0/1044/5 "2025-11-11T14:52:55Z")
Understood and yes, I think the only real case for block-mode RWX is likely Kubevirt so that is good to hear.