DE 

//Cloudogu EcoSystem Docs

  1. docs.cloudogu.com
  2. User manual
  3. Automatic Migration
  4. How-To Guides
  5. Final migration
Getting Started
User manual
Developer documentation

Final migration

The "final migration" differs from the other migration runs ("delta migration") in the following points:

  • The "final migration" is executed at a fixed specified time.
  • No further migration runs are executed after the "final migration".
  • The "final migration" puts the source instance into maintenance mode so that it is no longer used and no more changes are made there.
  • After the "final migration" an FQDN change can be carried out so that the target instance can then be reached under the FQDN of the source instance.

Time of the final migration

The "final migration" is executed at the configured time. If no time is configured, no "final migration" is executed. If the configured time is in the past, no further migration is carried out. If a "delta migration" is already being carried out at the configured time, the "final migration" waits until the "delta migration" has been completed. The "final migration" is then executed.

Maintenance mode in the source instance

At the start of the "final migration" the source instance is put into maintenance mode. As a result, the web interface of the source instance is no longer accessible and a web page with a corresponding message is displayed instead. This message can be configured.

The purpose of activating maintenance mode is to ensure that no further changes can be made to the source instance. This is to ensure that the data of the target instance corresponds to that of the source instance after the "final migration".

If the "final migration" is successful, the maintenance mode remains activated in the source instance and the target instance can now be used. However, if the "final migration" ends with an error, the maintenance mode in the source instance is deactivated again so that work in the source instance is still possible. In this case, you must configure a new time for the final migration.

Transferring the FQDN of the source instance

During the "final migration" the FQDN of the source instance can be transferred to the target instance. This ensures that work with the Dogus can continue under the same FQDN (now on the target instance) after the successful migration. In this case, the associated DNS entry must then refer to the IP address of the target instance.

Migration without transferring the FQDN of the source instance

If you do not transfer the FQDN of the source instance to the target instance, please note:

  • Repositories checked out from the SCM Manager still expect their remote under the old FQDN. Adapt this locally to the new FQDN.
  • If you customize the UI with the whitelabeling dogu and the associated data is stored in the instance, reconfigure the address of the whitelabel archive.
  • Adapt configured URLs in plugins to the new instance. This applies, for example, to plugins in the SCM Manager or Jenkins Dogu.
  • Adapt the URLs of configured baselines in the Baseline Dogu to the new FQDN.

Configuration

The configuration of the "final migration" must be specified in the CES importer on the target instance. This is configured in the custom resource of the CES component ("Component-CR") of the CES importer:

  • Edit the "Component-CR" of the CES Importer:

    kubectl edit component ces-importer -n ecosystem
  • Enter the desired configuration under config/migration/... in the valuesYamlOverwrite field

  • Example:

    apiVersion: k8s.cloudogu.com/v1
kind: Component
metadata:
  name: ces-importer
  namespace: ecosystem
spec:
  name: ces-importer
  namespace: k8s
  version: 1.0.0
  valuesYamlOverwrite: |
    config:
      migration:
        finalSchedule: "2025-04-03T12:34:56Z"
        changeFQDN: true
        maintenanceModeMessage:
          title: "Migration in progess."
          text: "The migration of your instance is in progress."
  • Save the changes to the component-CR

  • Restart the CES importer:

    kubectl rollout restart deployment/ces-importer -n ecosystem

Configure time

Specify the time at which the "final migration" is to be started config/migration/finalSchedule. The specification is made as a time stamp in RFC-3339 format. For example 2025-04-03T12:34:56Z. This corresponds to 34 minutes and 56 seconds after the 12th hour of April 4, 2025 in UTC.

Configuring the transfer of the FQDN of the source instance

If the FQDN of the source instance is to be transferred to the target instance, specify as true under config/migration/changeFQDN.

Note: If the FQDN is adopted, the associated DNS entry must be adjusted accordingly so that it points to the IP address of the target instance.

Configure message content in maintenance mode

During the "final migration" the maintenance mode is activated in the source instance. When maintenance mode is activated, a corresponding message is displayed in the source instance. Configure the title and text of this message under config/migration/maintenanceModeMessage/title or config/migration/maintenanceModeMessage/text.