//Cloudogu EcoSystem Docs

Domain Change

A domain change is not possible with the automatic migration.

Setting Up the Automatic Migration

When setting up the automatic migration, the target system must have the same domain configuration as the source system.
Otherwise, the LDAP Dogu—which is a prerequisite for the login process—cannot be started.

To check whether the domains of the source and target instances are identical, you can verify them in the systems.

Source instance:
etcdctl get /config/_global/domain
target system:
kubectl get configmap global-config -n ecosystem -o jsonpath='{.data.config\.yaml}' | grep '^domain:'

Domain via Blueprint

Since the Blueprint of the target system overwrites the migrated configuration again, it must be ensured that the target system Blueprint contains the same domain as the source system.

Alternatively, the domain can be omitted from the target system Blueprint. In this case, this configuration entry will not be overwritten again after the migration.