//Cloudogu EcoSystem Docs

Blueprints During Migration

The Blueprint Operator uses a mechanism to continuously reconcile the system based on a given specification.

CAUTION

Potential data loss may occur if the Blueprint Operator remains active during a migration.

If a Blueprint is present in the target system, the Blueprint Operator continuously attempts to reconcile the system state with the desired state defined in the Blueprint.

This would cause configurations applied by the automatic migration to potentially be overwritten or reverted.

Stopping Existing Blueprints

For this reason, Blueprints are disabled or stopped during the migration. This prevents them from being further processed by the Blueprint Operator.

apiVersion: k8s.cloudogu.com/v3
kind: Blueprint
...
spec:
  Stopped: true

Restarting Stopped Blueprints

If a Blueprint was active in the target system at the time of migration, it will be restarted after the migration has completed.

apiVersion: k8s.cloudogu.com/v3
kind: Blueprint
...
spec:
  Stopped: false

However, this may result in the configurations adopted during migration being overwritten again by the Blueprint.

Manually Stopped Blueprints

During the migration, all active blueprints are temporarily deactivated and reactivated after the import has completed.
The migration process only restarts those blueprints that it has previously stopped itself.

Blueprints that were already in a stopped state before the migration remain inactive after the migration.
This typically applies to blueprints that were intentionally paused for testing or transitional purposes but have not yet been deleted.

Under normal production conditions, there should be no manually stopped blueprints present.
If this is nevertheless the case, a manual review and, if necessary, explicit reactivation after the migration is required.