Prepare for an upgrade¶

The following preparation steps are required and must be completed prior to initiating a DataRobot application upgrade:

1. Review the general DataRobot requirements and the specific requirements for your platform.

   • Requirements Overview

2. Ensure you have access to the required container images for your target version.

   • Container Images Guide

3. Back up DataRobot database and configuration prior to upgrade.

   • Backup and restore

4. Gather the DATAROBOT_NAMESPACE value, which is the namespace where the DataRobot application is installed. Use the following command to list installed dr releases and check the "NAMESPACE" column:

   helm list -A --filter '^dr'
   export NAMESPACE="DATAROBOT_NAMESPACE"
   

   Note

   Replace DATAROBOT_NAMESPACE with your DataRobot namespace.

5. Determine if DataRobot was installed using Limited Admin Permissions. This is the case if the admin-privileges chart is installed. Check for the chart's presence by executing:

   helm list -A --filter admin-privs
   

6. For versions earlier 11.x check avalible storage space. DataRobot includes a PostgreSQL upgrade utility that backs up the data directory. This requires additional storage:

   • If your storage mount has less than ~25% available storage space (relative to the PostgreSQL data directory size), the PostgreSQL upgrade might fail.
   • For example, if your PostgreSQL data directory is 100GB, you need an additional 100GB to back up the old data and another 100GB for the new PostgreSQL data directory.
   • You can delete the old data directory after the upgrade is complete and validated.

   Check storage availability on the primary PostgreSQL pod.

   kubectl exec -it -n ${NAMESPACE} pcs-postgresql-0 -- bash -c "df -kh /bitnami/postgresql"
   

7. Review Application-level TLS configuration. DataRobot requires application-level TLS for inter-service communication. This requires cert-manager to be available. See the TLS requirements for more details.