7. Migration to v0.41.0

When you upgrade from a previous version to v0.41.0, you must update your configuration so that the OX Connector can run through the following procedure in the init-db container. The first startup can take some time, because of the full synchronization.

1. Detect empty database tables.

2. Recreate the subscription to the Provisioning Service.

3. Trigger a full synchronization of all UDM objects to the OX Connector.

4. Create the cache in the database.

Warning

Before you upgrade from a previous version to v0.41.0 go through the migration steps. Otherwise, the OX Connector fails during start.

Go through the following steps to update your configuration:

1. Create a PostgreSQL user and empty database for the OX Connector, see Configure a database.

2. Provide a PostgreSQL database connection URL through the openXchange.oxDbConnectionString Helm value in your custom values file. See Prepare configuration.

3. Retrieve the administrative credentials for the Provisioning Service of your Nubus for Kubernetes deployment. For information about how to retrieve these credentials, refer to Obtain administrative credentials in Univention Nubus - Customization and Modification Manual [1].

   Tip

   Use existing Kubernetes secrets

   Instead of specifying passwords directly in the values file, you can reference existing Kubernetes secrets. When you use existing secrets, Helm ignores the inline password values.

4. Provide the provisioning admin credentials through the following Helm Chart values:

   • provisioningApi.resync.auth.username and provisioningApi.resync.auth.password

   • or provisioningApi.resync.auth.existingSecret

5. Run helm upgrade as described in Listing 6.3 in Install consumer.