opendesk/docs/migrations.md

Upgrade migrations

• Disclaimer
• From v0.9.0
  • Automated migrations
    • Updated IAM component Nubus
• From v0.8.1
  • Updated cluster.networking.cidr
  • Updated customizable template attributes
  • migrations S3 bucket

Disclaimer

We do not offer support for upgrades before we reach openDesk 1.0.

Though we try to ease the pain when it comes to 0.x upgrades. That is what this document is for.

From v0.9.0

Automated migrations

Updated IAM component Nubus

openDesk is integrating the latest Nubus development from Univention. The new redundant and scalable LDAP requires migration activities. These have been automated to avoid manual interaction. The run_2 of the openDesk upgrade migrations executes the following steps

• Stage PRE:
  • Scale down statefulset/ums-ldap-server and statefulset/ums-ldap-notifier.
  • Create two new PVCs shared-data-ums-ldap-server-primary-0 and shared-data-ums-ldap-server-primary-1 for the new LDAP primary pods as copy from the existing shared-data-ums-ldap-server-0. The LDAP secondaries will sync from the primary nodes.
• Stage POST:
  • Restart Keycloak.
  • Cleanup: Delete the no longer used shared-data-ums-ldap-server-0 and shared-run-ums-ldap-server-0.

Note: You should ensure you have a backup of the contents of shared-data-ums-ldap-server-0 if something goes wrong during the upgrade migration.

From v0.8.1

Updated cluster.networking.cidr

• Action: cluster.networking.cidr is now an array (was a string until 0.8.1), please update your setup accordingly if you explicitly set this value.
• Reference:cluster.yaml

Updated customizable template attributes

• Action: Please ensure you update you custom deployment values according with the updated default value structure.
• References:
  • functional. prefix for authentication.*, externalServices.*, admin.* and filestore.*, see functional.yaml.
  • debug. prefix for cleanup.*, see debug.yaml.
  • monitoring. prefix for prometheus.* and graphana.*, see monitoring.yaml.
  • smtp. prefix for localpartNoReply, see smtp.yaml.

migrations S3 bucket

• Action: For self managed/external S3/object storages, please ensure you add a bucket migrations to your S3.
• Reference: objectstores.migrations in objectstores.yaml