Skip to content

Release v0.0.34

Choose a tag to compare

@github-actions github-actions released this 30 Oct 14:53
· 33 commits to main since this release
c632cef

openMCP

Components:

mcp-operator [v0.42.1]:

Changes included in v0.42.1:

πŸ› Fixes

  • update the controlplane resource even when in deletion #216
    • [USER][BUGFIX] Trigger the update of the ControlPlane resource even when CloudOrchestrator has a deletion timestamp

openmcp-operator [v0.16.0]:

Changes included in v0.16.0:

πŸš€ Features

  • release v0.16.0 #190
    • [USER][FEATURE] - Release v0.16.0
  • prepare for high availability #188
    • [OPERATOR][FEATURE] Add high availability features for the openmcp-operator and service-providers, cluster-providers and platform-services
  • exclude provider fields from status update & utility to set these fields #187
    • [DEVELOPER][FEATURE] - Utility function for service providers to add the kinds of their managed resources to the ServiceProvider status

πŸ”§ Chores

  • remove namespace field from secret reference in AccessRequest status #183
    • [USER][BREAKING] Removed the status.secretRef.namespace field from AccessRequest resources which was added by accident. The access secrets are expected to be in the same namespace as the AccessRequest itself, so wherever this field is read, it can just be replaced with the AccessRequest's namespace.
  • improve the advanced clusteraccess library's abilities to mock fake clients in unit tests #186
    • [DEVELOPER][FEATURE] The advanced ClusterAccess library's capabilities regarding unit tests have been enhanced by adding a configurable FakeClientGenerator to the reconciler. If set, this function will be called when trying to build a client.Client out of an AccessRequest's kubeconfig secret. This enables the test code to inject fake client implementations into the reconciler's Access method and thereby removes the need for any test-specific coding in the controller's logic itself.

gitops-templates [v0.1.0]:

Changes included in v0.1.0:


control-plane-operator [v0.1.18]:

Changes included in v0.1.18:

πŸ› Fixes

  • go.mod dependencies #122
    • [DEPENDENCY][OTHER] Fixing dependencies errors because of pointer type declaration and usage error

quota-operator [v0.14.0]:

Changes included in v0.14.0:


project-workspace-operator [v0.19.0]:

Changes included in v0.19.0:


bootstrapper [v0.5.1]:

Changes included in v0.5.1:

πŸ› Fixes

  • serilization of componentReferences #97
    • [USER][BUGIFX] Fix serilization of componentReferences in component versions

service-provider-landscaper [v0.10.0]:

Changes included in v0.10.0:

πŸš€ Features

  • read own deployment configuration resource to get image pull secrets #152
    • [OPERATOR][FEATURE] Configure image pull secrets specified in the service provider deployment resource

service-provider-crossplane [v0.1.1]:

Changes included in v0.1.1:

πŸ”§ Chores

  • upgrade dependencies #49
    • [DEPENDENCY][OTHER] Fixing pointer type usage due to dependency updates

cluster-provider-gardener [v0.9.1]:

Changes included in v0.9.1:

πŸ› Fixes

  • preserve metadata fields #141
    • [USER][FEATURE] Allow to use the metadata field of the Shoot Template in the ProviderConfig

cluster-provider-kind [v0.0.15]:

Changes included in v0.0.15:

πŸš€ Features

  • add script for local development #70
    • [DEVELOPER][FEATURE] Add scripts for enabling local development with cluster-provider-kind.

platform-service-dns [v0.0.2]:

Changes included in v0.0.2:

πŸ”§ Chores

  • bug fixes and secret copying #21
    • [OPERATOR][BREAKING] The structure of the DNSServiceConfig CRD changed slightly: spec.secretsToCopy was an array before, now it is a struct with the toPlatformCluster and toTargetCluster fields that contain the array which was on the top-level field before.
    • [OPERATOR][BUGFIX] Fixed some bugs related to the validation of the DNSServiceConfig CRD.
    • [OPERATOR][BUGFIX] Fixed a bug where the HelmRelease manifest was generated incorrectly if a helm chart in an OCI registry was referenced.
    • [OPERATOR][FEATURE] In addition to copying secrets from the provider namespace (on the platform cluster) into the cluster namespace (also on the platform cluster), it is now also possible to copy secrets into the namespace on the target cluster where the external-dns helm chart is deployed into.