v0.11.0

Changed

• [#34] Add/Update label for consistent mass deletion of CES K8s resources
  • Select any k8s-ces-setup related resources like this: kubectl get deploy,pod,... -l app=ces,app.kubernetes.io/name=k8s-ces-setup
  • Select all CES components like this: kubectl get deploy,pod,... -l app=ces
  • Update ces-build-lib to 1.61.0

Fixed

• [#32] Fixed a permission issue where the setup finisher cronjob was not allowed to execute his finisher script.

v0.10.0

Fixed

• [#30] The ecosystem-certificate TLS secret will now be created during setup.

v0.9.0

Fixed

• [#28] Setup wrongly assumed that all service accounts are of type dogu when creating step to wait for
  for them. Now only steps for dogu service accounts are created.

v0.8.1

Fixed

• [#26] Use correct label for dogu resources
  • dogu.name=name is now valid

Changed

• [#24] Read dogu registry URL schema from cluster secret instead of config.

v0.8.0

Changed

• [#22] If the resource urls from the k8s-components e.g. dogu-operator have the same host as the configured
  dogu registry, basic auth will be used for those components.
• [#22] Update makefiles to version 7.0.1
• [#22] Update ces-build-lib to version 1.56.0

v0.7.1

Fixed

• Internal release bugfix

v0.7.0

Changed

• [#20] Update internally used dependency versions
  • Update cesapp-lib to version v0.4.0
  • Update k8s-apply-lib to version v0.4.0
  • Update k8s-dogu-operator to version v0.11.0

v0.6.0

Changed

• [#17] Update makefiles to version 6.0.3

Fixed

• [#17] Change order of certificate chain und use unique serial number in generation.

Changed

• Extract client to apply k8s resources into own repository
  (https://github.com/cloudogu/k8s-apply-lib)

v0.5.0

Added

• [#12] Implement the registryConfigEncrypted section from the setup.json. Setup creates secrets for these values which can be processed by the k8s-dogu-operator.

v0.4.0

Added

• [#10] Automatic setup process with setup.json. See custom setup configuration for more information.