Releases: cloudogu/ecosystem-core
Releases · cloudogu/ecosystem-core
v4.1.0
Added
- [#56] Option
defaultConfig.env.initialDomainin Helm values to set a custom domain- This change is necessary because once we have the LOP-IDP component,
we need to have the correct domain set when it is installed because we do not support domain changes in LDAP.
- This change is necessary because once we have the LOP-IDP component,
Changed
- Default for the domain in the global config is now
ces.localdomainas*.localshould be used for mDNS only.
v4.0.0
Changed
- [#58] update components to newest versions:
- k8s-component-operator-crd 1.10.0 -> 1.14.0
- k8s-component-operator 1.12.0 -> 1.12.2
- k8s-dogu-operator-crd 2.11.0 -> 2.13.0
- k8s-dogu-operator 3.18.0 -> 3.21.0
- k8s-service-discovery 4.0.0 -> 6.0.1
- k8s-blueprint-operator 3.1.0 -> 3.2.0
- k8s-ces-gateway 2.0.1 -> 3.0.3
- k8s-ces-assets 1.0.4 -> 2.0.2
- k8s-ces-control 1.8.0 -> 1.10.3
- k8s-debug-mode-operator 1.0.0 -> 1.0.2
- k8s-backup-operator-crd 1.7.0 -> 1.8.0
- k8s-backup-operator 2.1.0 -> 3.0.3
- k8s-velero 10.0.1-5 -> 11.4.0-2
- k8s-prometheus 75.3.5-3 -> 75.3.5-5
- k8s-loki 3.3.2-6 -> 3.5.10-1
- k8s-promtail 2.9.1-9 -> 2.9.17-1
- k8s-alloy 1.1.2-1 -> 1.1.2-3
- k8s-support-archive-operator 1.1.0 -> 1.1.1
v3.0.2
v3.0.1
v3.0.0
** BREAKING CHANGES **
Changed
- [#45] Make the applying of the fqdn configurable and set the default to
false.- This can now break installations of ecosystem-core in development environments where no dns is used for the ecosystem fqdn.
- To enable it again, set the following helm value to
true:defaultConfig.env.enableFqdnApplier. - In production environments it is required to set the fqdn via the blueprint.
v2.2.2
Fixed
- [#43] Modify hooks for the job config templates
- The config job creates the global-config for the service-discovery, and the service-discovery creates the loadblancer service needed by the job.
- Use ArgoCD Sync Hooks because both the job and the component installations need to run at the same time.
- Use helm post-hooks because of the same reason.
- The config job creates the global-config for the service-discovery, and the service-discovery creates the loadblancer service needed by the job.