Skip to content

chore: Update dependency piraeus-operator to v2.11.0 - #193

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/piraeus-operator-2.x
Open

chore: Update dependency piraeus-operator to v2.11.0#193
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/piraeus-operator-2.x

Conversation

@renovate

@renovate renovate Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
piraeus-operator minor v2.10.8v2.11.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

piraeusdatastore/piraeus-operator (piraeus-operator)

v2.11.0

Compare Source

We are happy to announce a new feature release of our Operator!

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.maxConcurrentEvacuations to 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-group label 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.2
    • LINSTOR CSI 1.12.0
    • LINSTOR Affinity Controller 1.5.0
    • DRBD Reactor 1.12.0
Fixed
  • Fix detection of VolumeGroupSnapshots API.

Configuration

📅 Schedule: (in timezone UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from gurinderu as a code owner August 4, 2026 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants