Skip to main content

Migrating to 2.5.0

Migration Guide​

Here you can find the needed steps to upgrade your current Witboost installation to v2.5.0. Please refer to the release notes for a detailed list of changes and improvements. This guide is intended for users who are currently running Witboost version 2.4.0 or earlier and wish to upgrade to version 2.5.0.

Follow these steps to migrate from the previous version to Witboost version 2.5.0:

Backup Your Data​

Before starting the migration, ensure you have a complete backup of your database and configuration files.

Update Dependencies​

Ensure all the dependencies in the Helm files are updated to their compatible versions for 2.5.0. Refer to the published Helm chart for details.

Upgrade Steps​

Provisioning Coordinator​

  • If you already splitted Coordinator and CGP services, no additional steps are required.

  • If you are still running Coordinator and CGP services within the same server, but you're using our official chart, no additional steps are required.

Instead, if you're running Coordinator and CGP services within the same server with a custom chart, be sure to mount and make the Witboost license available to CGP:

Declare a new volume in the deployment.yaml of the chart, under spec.template.spec.volumes like this:

- name: license
  secret:
    secretName: witboost-secrets

and then mount it in the main service container under spec.template.spec.containers[i].volumeMounts like this:

- name: license
  readOnly: true
  mountPath: "/app/license"
  subPath: CORE_LICENSE_FILE
- name: license
  readOnly: true
  mountPath: "/app/signature"
  subPath: CORE_SIGNATURE

Computational Governance Platform (CGP)​

  • If you already splitted Coordinator and CGP services and you're using our official chart, no additional steps are required.

Instead, if you're using a custom chart, be sure to mount and make the Witboost license available to CGP:

Declare a new volume in the deployment.yaml of the chart, under spec.template.spec.volumes like this:

- name: license
  secret:
    secretName: witboost-secrets

and then mount it in the main service container under spec.template.spec.containers[i].volumeMounts like this:

- name: license
  readOnly: true
  mountPath: "/app/license"
  subPath: CORE_LICENSE_FILE
- name: license
  readOnly: true
  mountPath: "/app/signature"
  subPath: CORE_SIGNATURE