fix(deps): update module github.com/openmcp-project/openmcp-operator/lib to v0.12.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
github.com/openmcp-project/openmcp-operator/lib	require	minor	v0.10.0 -> v0.12.0

---

Release Notes

openmcp-project/openmcp-operator (github.com/openmcp-project/openmcp-operator/lib)

v0.12.0

Compare Source

Changes included in v0.12.0:

🔨 Refactoring

• [breaking] [operator] AccessRequest api #​141: The AccessRequest resource has been refactored for a better differentiation between token and oidc access requests.

🐛 Fixes

• [bugfix] [operator] fix cluster printer columns #​140: The additional printer columns for the Cluster resource will now correctly show up on kubectl get.
• [bugfix] [operator] remove namespace from ClusterProfile's provider and providerconfig references #​138: The providerRef and providerConfigRef fields in the ClusterProfile's spec now only take a name and no namespace, as intended.

v0.11.2

Compare Source

Changes included in v0.11.2:

🚀 Features

• [feature] [developer] add RoleRef support #​137: Adding support in the lib to reference RoleRefs in the ClusterAccess reconciler.
• [feature] [user] cluster- and access-request names #​134: - Prevent name conflicts for ClusterRequests and AccessRequests
• [feature] [user] package crds in component #​133: Package the custom ressource definition manifests for the openmcp-operator into the OCM component
• [feature] [operator] install providers in system namespace #​126: Install all providers in a common namespace "openmcp-system"
• [feature] [operator] Allow override for 'run' and 'init' command in providers #​129: The init and run commands for providers can now be overwritten by using the respective fields in the spec of ServiceProvider, ClusterProvider, and PlatformService` resources.

🔧 Chores

• [breaking] [operator] remove onboarding cluster kubeconfig argument #​130: The openmcp-operator now takes a --kubeconfig argument for the platform cluster kubeconfig instead of the previous --platform-cluster argument. The --onboarding-cluster argument has been removed to make the operator work without an existing onboarding cluster.

v0.11.1

Compare Source

Changes included in v0.11.1:

🚀 Features

• [feature] [user] add RoleRefs to AccessRequest API ##​128: Adding support for role references in AccessRequests to bind the ServiceAccount to an existing role or cluster role.
• [feature] [operator] use K8sNameUUID instead of K8sNameHash and let each mcp have its own namespace ##​114: The library functions regarding stable MCP namespace and request names have been adapted to use the new UUID-style hash functions and the concept of each MCP having its own namespace on the platform cluster.

v0.11.0

Compare Source

Changes included in v0.11.0:

🚀 Features

• [feature] [user] add ExtraVolumes and ExtraVolumeMounts to DeploymentSpec #​118: Adding ExtraVolumes and ExtraVolumeMounts fields to the DeploymentSpec
• [feature] [user] add name field to AccessRequest permissions #​113: It is now possible to overwrite the name of (Cluster)Roles generated by AccessRequests.
• [feature] [operator] add extra scopes to oidc provider config #​108: It is now possible to specify additional scopes for OIDC providers (in AccessRequest and ManagedControlPlane api types).
• [feature] [user] add ManagedControlPlane API #​104: Added the ManagedControlPlane type with api version core.openmcp.cloud/v2alpha1 and added OIDC configuration to the AccessRequest type.

🐛 Fixes

• [bugfix] [user] add ExtraVolumes and ExtraVolumeMounts to DeploymentSpec #​118: Fixing permission issues on ClusterProfiles during Init job of Cluster Providers and Service Providers

🔧 Chores

• release v0.11.0 #​120.
• [bugfix] [operator] remove broken validation rule #​111: Removed a broken validation rule that made it impossible to apply the AccessRequest CRD.
• [breaking] [user] rename v2 MCP resource #​109: The v2 ManagedControlPlane resource has been renamed to ManagedControlPlaneV2 to avoid k8s trying to convert between v1 and v2, since we want to use both in parallel for the migration period.

---

Configuration

📅 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.

---

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

---

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

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 5 additional dependencies were updated

Details:

Package	Change
github.com/openmcp-project/controller-utils	v0.16.0 -> v0.19.0
github.com/openmcp-project/openmcp-operator/api	v0.10.0 -> v0.12.0
github.com/fluxcd/pkg/apis/kustomize	v1.10.0 -> v1.12.0
github.com/openmcp-project/controller-utils/api	v0.16.0 -> v0.19.0
golang.org/x/exp	v0.0.0-20250718183923-645b1fa84792 -> v0.0.0-20250819193227-8b4c13bb791b

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.