Release v0.0.4

Changes included in v0.0.4:

🔧 Chores

• update openmcp-operator to v0.17.0, and release v0.0.4 #41
  • [USER][FEATURE] - Update openmcp-operator to v0.17.0
    • Release v0.0.4

Release v0.0.3

Changes included in v0.0.3:

🔨 Refactoring

• use advanced clusteraccess library #30
  • [DEVELOPER][OTHER] The controller now uses the advanced clusteraccess library instead of managing access to the clusters itself.

📚 Documentation

• update examples in documentation #31
  • [USER][DOC] Updated the examples in the configuration documentation.

🚀 Features

• release v0.0.3 #40
  • [DEVELOPER][FEATURE] - Release v0.0.3
• also copy image pull secrets referencedin PlatformService spec #29
  • [USER][FEATURE] All secrets referenced in spec.imagePullSecrets in the provider's PlatformService resource are now copied to both, the platform cluster (in the cluster namespace) and the target cluster (in the external-dns deployment namespace). This happens in addition to any secret copying configured in the service configuration.

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

Release v0.0.1

Changes included in v0.0.1:

🚀 Features

• external-dns cluster controller #12
  • [USER][FEATURE] The PlatformService DNS now reconciles Cluster resources. If a cluster's purposes match one of the mappings provided in the controller's configuration (provided via the DNSServiceConfig resource), external-dns is deployed onto the cluster, with its configuration determined by the aforementioned mapping.