myCloudogu // Docs

Ensure equality in source and target instance

The versions of the Dogus must match exactly in the source instance and the target instance. The migration is not carried out if there are version differences.

Procedure

Establish dogu equality
- Dogus can be installed in the target system or deleted in the source system
- Note: nginx-, Backup-, Registrator- & Monitoring-Dogu were implemented differently in CES-MN and are ignored when determining the dogu equality (see explanation)
Establish version consistency
- The easiest way to achieve version consistency is to install the same blueprint in both instances. If this is not possible, the versions must be adjusted manually.
- The versions of all Dogus can be displayed as follows:
  - CES-VM: cesapp list
  - CES-MN: kubectl get dogus.
- Since versions cannot be downgraded, the versions in both systems should be compared and adjusted in the instance with the lower version
  - CES-VM: cesapp upgrade dogu <doguName> <doguVersion>
  - CES-MN
```
apiVersion: k8s.cloudogu.com/v2
kind: Dogu
metadata:
name: <doguName>
labels:
  app: ces
spec:
name: <doguNamespace>/<doguName>
version: <doguVersion>
```
Establish component equality
- All components in the source system must be installed in the same version in the target system
- Additional components may be installed in the target system

Questions? Hints? Discuss!

Ensure equality in source and target instance
- Procedure