This is the first release candidate for the upcoming 2.11.0 release. It contains a number of improvements that warrent a longer release phase for testing.
The Operator itself gained support for limiting the number of concurrent evacuations using the new LinstorCluster.spec.maxConcurrentEvacuations key. It also now allows passing arguments to lvcreate, zpool create, etc... on storage pool creation.
On the new component feature front, we have added support for consistency groups in volumes. This ensures that in event of node failures, as workload using multiple volumes at once see a consistent state of the data on the new host after fail over.
We also implemented optional Quality of Service settings for volumes. These require an NRI plugin that enforces the necessary limits on Pod startup. See here for how to configure QoS for your volumes.
We also have the usual round of improvements and bug fixes by updating our components. LINSTOR itself should be faster to start up on first deployment. LINSTOR CSI should be more robust when validating RWX modes, along with the usual dependency updates.
Added
- Allow configuring the separator between generated Satellite resource names and the Satellite name.
- Add
LinstorCluster.spec.maxConcurrentEvacuationsto limit how many Satellites are evacuated at the same time, for both direct and ClusterAPI-driven node removals. - Enable consistency groups in LINSTOR CSI: PersistentVolumeClaims sharing a
linstor.csi.linbit.com/consistency-grouplabel are placed as separate volumes of one LINSTOR resource, ensuring a fail-over node always sees a consistent view across the whole set of volumes.
Changed
- Updated images:
- LINSTOR 1.34.1
- LINSTOR CSI 1.12.0
- LINSTOR Affinity Controller 1.5.0
- DRBD Reactor 1.12.0