Equality of source instance and target instance
The equality of the source and target instance can be looked at from several perspectives. Firstly, version equality between the source and target instance is required to ensure the migration can happen at all. This requirement applies both to the migration from a CES-VM instance to a CES-MN instance, and to the migration from a CES-MN instance to another CES-MN instance. On the other hand, the question arises as to how the source and target instances are the same after migration.
Equality when migrating from a CES VM instance to a CES MN instance
Migration requirements
Dogu versions must be the same because:
- Dogus between different versions require different migrations of their own. We avoid these complications through version consistency.
- The same versions have the same configurations. This makes migration easier and avoids inconsistencies.
Exceptions
The following Dogus are disregarded for equality, as they do not exist on CES-MN instances:
- premium/backup
- official/monitoring
- official/registrator
-
official/nginx
- nginx is replaced by nginx-static and nginx-ingress in CES-MN instances
- nginx must be at least version 1.28.0-2 on the exporting instance
Equality and comparability after migration
- Because of the architectural differences between a CES VM instance and a CES MN instance there can be no absolute equality between the source and target instances.
-
Everything should work the same for end users on the user interface after the migration.
- Exceptions are of course Dogus, which are not migrated.
- If the FQDN is also migrated, the migration is ideally not noticeable at all.
Equality when migrating from one multinode instance to another multinode instance
Coming soon