Release v0.17.0
Changes included in v0.17.0:
🚀 Features
-
release v0.17.0 #198
- [OPERATOR][FEATURE] - Release v0.17.0 of the github.com/openmcp-project/opencmp-operator
-
allow to control the high availability config of ps mcp #191
- [OPERATOR][FEATURE] Allow to configure number of replicas and topology spread constraints of the platform service managed control plane.
-
user-friendly secret name for MCP access #193
- [USER][FEATURE] New name pattern for MCP access secrets on the onboarding cluster. The secret name clearly refers to the corresponding MCP IAM spec values as follows:
<provider-name>.<mcp-name>.kubeconfigwhere provider-name is either an OIDC provider or static token name.
- [USER][FEATURE] New name pattern for MCP access secrets on the onboarding cluster. The secret name clearly refers to the corresponding MCP IAM spec values as follows:
🔧 Chores
- enable ClusterAccessReconciler's Reconcile method to be called during deletion #197
- [DEVELOPER][FEATURE] The ClusterAccess Reconciler's
Reconcilemethod can now be called during the deletion logic of the embedding controller without re-creating resources that have already been deleted by an earlierReconcileDeletecall. This meansReconcilecan now be called at the beginning of a deleting reconciliation andReconcileDeleteat the end, without resources being created and deleted endlessly when walking through this deletion flow multiple times (because the request is reconciled multiple times because it needs to wait for resources being deleted).
- [DEVELOPER][FEATURE] The ClusterAccess Reconciler's
- enable provider webhooks #195
- [OPERATOR][FEATURE] During provider deployment, it is now checked whether a webhook TLS secret exists for the provider being deployed. If so, it is automatically mounted in the run container. The name of the mounted secret is determined by the new
WebhookSecretNamefunction from thelib/utilspackage.
- [OPERATOR][FEATURE] During provider deployment, it is now checked whether a webhook TLS secret exists for the provider being deployed. If so, it is automatically mounted in the run container. The name of the mounted secret is determined by the new