chore(deps): update dependency openmcp-project/openmcp-operator to v0.11.1 #43
  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:
v0.9.1->v0.11.1v0.11.2Release Notes
openmcp-project/openmcp-operator (openmcp-project/openmcp-operator)
v0.11.1Compare Source
Changes included in v0.11.1:
🚀 Features
v0.11.0Compare Source
Changes included in v0.11.0:
🚀 Features
ExtraVolumesandExtraVolumeMountstoDeploymentSpec#118: AddingExtraVolumesandExtraVolumeMountsfields to theDeploymentSpecManagedControlPlaneAPI #104: Added theManagedControlPlanetype with api versioncore.openmcp.cloud/v2alpha1and added OIDC configuration to theAccessRequesttype.🐛 Fixes
ExtraVolumesandExtraVolumeMountstoDeploymentSpec#118: Fixing permission issues onClusterProfilesduring Init job of Cluster Providers and Service Providers🔧 Chores
ManagedControlPlaneV2to avoid k8s trying to convert between v1 and v2, since we want to use both in parallel for the migration period.v0.10.0Compare Source
Changes included in v0.10.0:
🚀 Features
ClusterRequestresources can now be configured to delay the removal of their own finalizer (therefore also delaying their own deletion) until the correspondingClusteris gone when the request is deleted, instead of the finalizer being removed immediately after the deletion of the Cluster has been triggered. Cluster providers need to take care to implement the feature accordingly. Thespec.waitForClusterDeletionflag has no effect in situations where deletion of theClusterRequestdoes not trigger a deletion of the correspondingCluster.ServiceProviderresources must now expose a list of their service resource types in their status. Service providers must take care to implement the feature accordingly. This serves as a kind of 'service catalog' that allows to look up the k8s resources that belong to a specific service provider.🔧 Chores
🐛 Fixes
AccessRequestConfigduring controller start up #96: Fixing possible nil pointer dereference bug while accessing emptyAccessRequestConfigduring start up of accessrequest controllerConfiguration
📅 Schedule: 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 is behind base branch, 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.