fix(deps): update module github.com/openmcp-project/cluster-provider-gardener/api to v0.9.0 #205
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.8.1->v0.9.0Release Notes
openmcp-project/cluster-provider-gardener (github.com/openmcp-project/cluster-provider-gardener/api)
v0.9.0Compare Source
Changes included in v0.9.0:
🚀 Features
Clustercontains other finalizers than its own one. This allows other controllers with finalizers on theCluster- likely because they deployed something on the cluster - to cleanup first before the cluster is deleted, thereby potentially preventing leaked/orphaned resources.GrouporUserin anAccessRequest'sspec. oidc.roleBindings[*].subjectsentry, it is now possible to prefix thenamewith::. This will cause the ClusterProvider to just remove this prefix instead of applying the oidc provider name when creating (Cluster)RoleBindings out of this configuration. By using this method, it is now possible to bind to k8s-predefined Groups such assystem:authenticatedby specifying::system:authenticatedas subject name, for example.🔧 Chores
AccessRequestresources are now named<access-request-name>.kubeconfig. Before, they were just named like the owningAccessRequestitself. Existing secrets with the old name will continue to exist until theAccessRequestis removed, but they will not be updated anymore.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.
This PR was generated by Mend Renovate. View the repository job log.