chore: Update dependency piraeus-operator to v2.11.0 - #193
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v2.10.8→v2.11.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
piraeusdatastore/piraeus-operator (piraeus-operator)
v2.11.0Compare 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.maxConcurrentEvacuationskey. 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
LinstorCluster.spec.maxConcurrentEvacuationsto limit how many Satellites are evacuated at the same time, for both direct and ClusterAPI-driven node removals.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
Fixed
Configuration
📅 Schedule: (in timezone UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.