Upgrade from DataRobot 11.x to the latest release¶

This section provides a checklist of tasks that are required when upgrading from any DataRobot 11.x version to the latest release version.

Upgrade to latest release¶

In the latest release, the PCS and DataRobot charts have been consolidated into a single chart. This change eliminates code duplication and simplifies the installation process.

Update values¶

The latest DataRobot release introduces minor changes to YAML configuration schema, therefore you must adjust the existing configuration to match a new schema.

Minimal values files¶

For platform-specific configuration examples, refer to the minimal values files located within the datarobot-prime/override Helm chart artifact directory.

tar xzf datarobot-prime-X.X.X.tgz
cd datarobot-prime/override 

Use the current values_dr.yaml files as reference when populating the minimal values files.

Upgrade GenAI¶

Enable the LLM Gateway service in values_dr.yaml. For details, see the Generative AI documentation.

Review custom CA bundle configuration¶

Review Custom CA bundle configuration¶

If you are using Trust Manager and deploying custom CA bundles to manage root certificates across the DataRobot platform, you must verify the structure of the ca-cert-bundle.yaml file. For details, see the "upgrade notes" section of Configuring Custom CA.

If you are using Trust Manager and deploying custom CA bundles to manage root certificates across the DataRobot platform, you must verify the structure of the ca-cert-bundle.yaml file. For details, see Configuring Custom CA.

Review notebook configuration¶

The naming for notebook chart values was updated this change may impact your process. For detailed instructions, see the Notebooks Upgrade Guide.

Application upgrade steps¶

Set DataRobot namespace¶

export NAMESPACE="DATAROBOT_NAMESPACE" 

Delete Elasticsearch certificate¶

kubectl -n ${NAMESPACE} delete secret pcs-elasticsearch-master-crt 

Temporary disable PostgreSQL HA¶

If High Availability (HA) is configured for PostgreSQL, reduce the PostgreSQL replicaCount to prevent potential conflicts during the upgrade procedure:

postgresql-ha:
    postgresql:
        replicaCount: 1 

Run Helm upgrade to latest version¶

helm upgrade --install dr datarobot-prime-X.X.X.tgz \
--namespace ${NAMESPACE} \
--values values_dr.yaml \
--debug \
--timeout 20m 

Post-upgrade tasks¶

After your helm upgrade command has completed successfully and the application pods are running, perform any applicable final steps from the sections below to complete the upgrade process.

Scale PostgreSQL replica¶

If High Availability (HA) for PostgreSQL is required, scale the PostgreSQL replica count back up to the desired value to restore HA functionality.

kubectl scale statefulset pcs-postgresql --replicas=3 -n ${NAMESPACE} 

postgresql-ha:
    postgresql:
        replicaCount: 3 

Upgrade GenAI¶

For every installation that includes a GenAI subsystem, you must run static files migration and execution environment migration. This is done automatically for installations with internet access, however, offline clusters must do this manually:

• Migrate static files.
• Migrate execution environments.