v3.8.2

Fixed

• [#248] Use correct user and group ids for the additionalMounts Init-Container.
  • Note that UIDs/GIDs need to be uniform for all dogu volumes, otherwise this feature may not work as expected
• [#248] update to image cloudogu/dogu-additional-mounts-init:0.1.2, so that user and group ids are set correctly.

v3.8.0

Added

• [#240] Init-Container creation for additionalMounts from the Dogu-CRD.
  The dogu-operator now supports mounting configmaps or secrets in dogus with the dogu-additional-mounts-init container.
  • If only the additionalMounts change and there is no dogu upgrade, the dogu.json used for this process is fetched from the local dogu registry.
  • Thus, you can add a new volume while developing a dogu and test the addtionalMounts.
  • On dogu upgrades the routine will always use the new dogu descriptor from remote.

v3.7.0

Fixed

• [#245] Check Replica count instead of readiness status at Dogu startup to prevent blocking operator when a Dogu cannot be started

v3.6.0

Changed

• [#239] Extracted Dogu-CRD, Dogurestart-CRD and associated clients to own repository
• [#242] Prevent decreasing volume size
• [#242] Update to dogu resource with new minimal volume size field

v3.5.1

Changed

• [#236] Set sensible resource requests and limits
• [#237] Set resource requests and limits in all containers of dogu, including init container

Fixed

• A bug where the operator would not register the new dogu version on upgrade.

v3.5.0

Fixed

• [#210] A bug where the operator tried to create a service account for example CAS when it was not healthy.
  This occurred in situations where the producer dogu got upgraded and immediately after that an installation with a service account create for that dogu happened.

v3.4.0

Added

• [#234] Add additional print columns and aliases to CRDs

v3.3.0

Added

• [#231] Export-Mode on Dogu-CR
  • This change adds an additional exporter-sidecar container to the pod of the dogu if the exportMode of a dogu is active

Changed

• [#231] Update to go v1.24.1
• [#231] Update dogu operator CRD to 2.5.0

v3.2.1

Removed

• [227] Remove allowPrivilegeEscalation flag

v3.2.0

Added

• [#225] Proxy support for the container and dogu registry. The proxy will be used from the secret ces-proxy which will be created by the setup or the blueprint controller.
• [#222] Functionality to set security-specific fields in Dogu descriptors and CRs.
  • These will be used to generate a security context for the deployment.