# Upgrade Datalore On-Premises (Helm installation)

The instructions below explain  how to upgrade Datalore On-Premises (Helm installation). The current latest version is 2026.3.

> **Note: Important**
> * When planning your upgrade to the latest version of Datalore, the upgrade process must be done in a sequential manner. Datalore upgrade mechanism requires you to step through each intermediate version as opposed to skipping straight to the most recent version. This is crucial to ensure the continuity, stability, and integrity of your system and data. We strongly recommend following the correct path from your current version to the desired version, acknowledging each intermediate version in the process. Failure to adhere to this can result in unforeseen compatibility issues, performance inconsistencies or data loss.
>
> * If you use a custom agent configuration, update agent images so that agent and server versions match after you upgrade Datalore.
>
> * Back up Kubernetes volumes before updating Datalore.

Procedure: Upgrade to version 2026.3

> **Note:**
> You should only upgrade to version 2026.3 if the current version is 2026.2 (all patch versions).
>
>
>
> To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.45
```

Procedure: Upgrade to version 2026.2.4

> **Note:**
> You should only upgrade to version 2026.2.4 if the current version is 2026.1 or 2026.2 (all patch versions).
>
>
>
> To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.44
```

Procedure: Upgrade to version 2026.2.3

> **Note:**
> You should only upgrade to version 2026.2.3 if the current version is 2026.1 or 2026.2 (all patch versions).
>
>
>
> To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.43
```

Procedure: Upgrade to version 2026.2.2

> **Note:**
> You should only upgrade to version 2026.2.2 if the current version is 2026.1 or 2026.2 (all patch versions).
>
>
>
> To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.42
```

Procedure: Upgrade to version 2026.2.1

> **Note:**
> You should only upgrade to version 2026.2.1 if the current version is 2026.1 (all patch versions).
>
>
>
> To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.41
```

Procedure: Upgrade to version 2026.1.1

> **Note:**
> You should only upgrade to version 2026.1.1 if the current version is 2025.6 (all patch versions) or 2026.1.
>
>
>
> To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.39
```

Procedure: Upgrade to version 2026.1

> **Note:**
> You should only upgrade to version 2026.1 if the current version is 2025.6 (all patch versions).
>
>
>
> To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.38
```

Procedure: Upgrade to version 2025.6.2

> **Note:**
> You should only upgrade to version 2025.6.2 if the current version is 2025.5, 2025.5.1, 2025.6, or 2025.6.1. To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.37
```

Procedure: Upgrade to version 2025.6.1

> **Note:**
> You should only upgrade to version 2025.5.1 if the current version is 2025.5, 2025.5.1, or 2025.6. To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.36
```

Procedure: Upgrade to version 2025.6

> **Note:**
> You should only upgrade to version 2025.6 if the current version is 2025.5, or 2025.5.1. To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.35
```

Procedure: Upgrade to version 2025.5.1

> **Note:**
> You should only upgrade to version 2025.5.1 if the current version is 2025.4, 2025.4.1, or 2025.5. To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.34
```

Procedure: Upgrade to version 2025.5

> **Note:**
> You should only upgrade to version 2025.5 if the current version is 2025.4 or 2025.4.1. To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.33
```

Procedure: Upgrade to version 2025.4.1

> **Note:**
> You should only upgrade to version 2025.4.1 if the current version is 2025.3.1 or 2025.4. To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.32
```

Procedure: Upgrade to version 2025.4

> **Note:**
> You should only upgrade to version 2025.4 if the current version is 2025.3.1. To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the `storage` and `postgresql-data` volumes.

3. Update the local cache of Helm chart repositories:

```BASH
helm repo update
```

4. Upgrade Datalore:

```BASH
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.31
```

Procedure: Upgrade to version 2025.3.1

> **Note:**
> You should only upgrade to version 2025.3.1 if the current version is 2025.2. To upgrade from an earlier version, apply each intermediate version in order. Skipping versions is not supported and may cause compatibility issues or data loss.

> **Warning:**
> The baseline Python interpreter in 2025.3.1 has been updated to Python 3.11.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.30
```

Procedure: Upgrade to version 2025.2

1. Back up the storage and postgresql-data volumes before upgrading.

2. Execute the `helm repo update` command.

3. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.28
```

Procedure: Upgrade to version 2025.1

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. (Optional) If you're still using secrets and notebook-level SSH keys or Git repositories, make sure to migrate those that you want to keep. Follow [this procedure](migrate-from-deprecated-features.html).

4. Execute the `helm repo update` command.

5. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.26
```

Procedure: Upgrade to version 2024.5.1

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. (Optional) Make sure you have migrated from [deprecated features](migrate-from-deprecated-features.html).

4. Execute the `helm repo update` command.

5. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.25
```

Procedure: Upgrade to version 2024.5

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. (Optional) Make sure you have migrated from [deprecated features](migrate-from-deprecated-features.html).

4. Execute the `helm repo update` command.

5. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.24
```

Procedure: Upgrade to version 2024.4.1

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.23
```

Procedure: Upgrade to version 2024.4

> **Warning:**
> This version includes PostgreSQL version migration from Postgres 12 to Postgres 15.
>
>
>
> If your Datalore installation uses an external database (not the one shipped with Datalore), we advise to upgrade the database instance using the database provider preferred tooling, or to reach out to your database administrator for further guidance.

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.22
```

Procedure: Upgrade to version 2024.3

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.21
```

Procedure: Upgrade to version 2024.2.3

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.20
```

Procedure: Upgrade to version 2024.2.2

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.19
```

Procedure: Upgrade to version 2024.2.1

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.18
```

Procedure: Upgrade to version 2024.2

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.17
```

Procedure: Upgrade to version 2024.1

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.16
```

Procedure: Check content output migration

Upgrade to 2024.1 involves an internal output migration, which we strongly recommend checking by performing the following steps.

1. When running the updated version (2024.1) for the first time, check Datalore server logs. The logs are expected to contain lines similar to the ones in the example below.

> **Note:**
> Timings, thread names and number of files presented in the example will differ from yours.

```
            12:44:03.931 INFO  [OutputsMigrationEDT] j.d.o.s.i.migration.OutputsMigrationTool Files to migrate: 313

12:44:04.205 INFO  [Thread-3] j.d.o.s.i.m.LoggingOutputMigrationProgressTracker Processed 4/313 (1%) file(s)
12:44:04.261 INFO  [Thread-2] j.d.o.s.i.m.LoggingOutputMigrationProgressTracker Processed 7/313 (2%) file(s)
...
12:44:05.324 INFO  [Thread-3] j.d.o.s.i.m.LoggingOutputMigrationProgressTracker Processed 313/313 (100%) file(s)
```

2. Check if there were any errors that occurred during the migration. Such errors will be listed as a short summary below the `Processed [n] 100% files` line. If no errors are found, no further steps need to be performed.

3. If there are any errors, save the IDs of notebooks together with the error messages. Scroll up the logs and find and save the respective stacktraces for these errors.

4. Use the saved IDs to try to open the notebooks with the migration errors. If any of these notebooks fail to open, contact Datalore support providing the error message and stacktrace for each such notebook.

Procedure: Upgrade to version 2023.6

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.14
```

Procedure: Upgrade to version 2023.5.1

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Remove the following blocks under `agentsConfig` in the `values.yaml` file:

```YAML
volumeMounts:
  - mountPath: /etc/datalore/logback-config
    name: logback-config
```

```YAML
volumes:
  - name: logback-config
    configMap:
      name: datalore-logback-config
```

5. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.13
```

Procedure: Upgrade to version 2023.5

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.12
```

Procedure: Upgrade to version 2023.4

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.11
```

Procedure: Upgrade to version 2023.3.1

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.10
```

> **Note:**
> The updating procedure involves checkpoint migration, which will cause the first startup of the new version to take longer than usual.

Procedure: Upgrade from 2023.1 to 2023.2

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.8
```

> **Note:**
> The updating procedure involves checkpoint migration, which will cause the first startup of the new version to take longer than usual.

Procedure: Upgrade from 2022.3 to 2023.1

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Back up the storage and postgresql-data volumes before upgrading.

3. Execute the `helm repo update` command.

4. (Optional) If you built [custom images](customize-or-update-environment.html) based on 2023.1 agent image, remove the following line from your custom image Dockerfile before rebuilding them:

```DOCKERFILE
ADD --chown=datalore:datalore https://raw.githubusercontent.com/JetBrains/datalore-configs/2023.1/misc/build_code_insight_data.sh /opt/datalore/build_code_insight_data.sh
```

5. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.7
```

Procedure: Upgrade from 2022.2.3 to 2022.3

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. (Optional) If you have disabled SMTP in your configs, remove the respective parameters.

3. Back up the storage and postgresql-data volumes before upgrading.

4. Execute the `helm repo update` command.

5. Change the `dbRootPassword: XXX` parameter in the `datalore.values.yaml` file to:

```
databaseSecret:
password: XXX
```

6. (Optional) Change the following parameter names in the `datalore.values.yaml` file if you have them set:

```
sqlServerHost > sqlCellsApiHost
sqlServerPort > sqlCellsApiPort
```

7. Restart Datalore by running the following commands:

```CONSOLE
helm uninstall datalore
helm upgrade --install -f datalore.values.yaml datalore datalore/datalore --version 0.2.6
```

> **Note: Important**
> The procedure assumes that you store your custom values in `datalore.values.yaml`, which is NOT the same as the earlier location (`charts/datalore/values.yaml`). See the [installation guide](install-datalore-on-premises-using-kubernetes-helm.html) for more details.

Procedure: Upgrade from 2022.2-2022.2.2 to 2022.2.3

* [Update Hub](update-hub.html) if your Datalore installation uses it.

* Execute the `helm repo update` command.

* Restart Datalore by running the following commands:

```CONSOLE
helm uninstall <release_name>
helm upgrade --install -f datalore.values.yaml <release_name> datalore/datalore
```

> **Note: Important**
> The procedure assumes that you store your custom values in `datalore.values.yaml`, which is NOT the same as the earlier location (`charts/datalore/values.yaml`).

Procedure: Upgrade from 2022.2 to 2022.2.1

* [Update Hub](update-hub.html) if your Datalore installation uses it.

* Update the `datalore-configs` repository to the [2022.2.1 branch.](https://github.com/JetBrains/datalore-configs/tree/2022.2.1)

* Restart Datalore by running the following commands:

```CONSOLE
helm uninstall <path_to_datalore-configs>/charts/datalore
helm upgrade --install -f datalore.values.yaml <path_to_datalore-configs>/charts/datalore
```

Procedure: Upgrade from versions 2021.3.5-2022.1.4 to 2022.2 (Helm installation)

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Update the `datalore-configs` repository to the [2022.2 branch](https://github.com/JetBrains/datalore-configs/tree/2022.2.1).

3. Change `FRONTEND_URL` to `DATALORE_PUBLIC_URL`.

4. Change the format of `dataloreEnv` to a helm map.

Old format:

```YAML
dataloreEnv: |
  export FRONTEND_URL="https://datalore.example.com"

  export HUB_PUBLIC_BASE_URL="https://hub.datalore.example.com/hub"
  export HUB_DATALORE_SERVICE_ID="XXX"
  export HUB_DATALORE_SERVICE_SECRET="YYY"
```

New format:

```YAML
dataloreEnv:
  DATALORE_PUBLIC_URL: "https://datalore.example.com"

  HUB_PUBLIC_BASE_URL: "https://hub.datalore.example.com/hub"
  HUB_DATALORE_SERVICE_ID: "XXX"
  HUB_DATALORE_SERVICE_SECRET: "YYY"
```

> **Note:**
> Consider the following:
>
> * `The ENABLE_PLANS` variable is unnecessary. Plans are enabled if the `plansConfig` helm variable is set.
>
> * `DEFAULT_PACKAGE_MANAGER="pip"` is a default setting now
>
> * `DEFAULT_BASE_ENV_NAME=minimal` is a default setting now.

Procedure: Data migration when upgrading to 2022.2 or later versions

Starting from version 2022.2, data directories are accessible under new names. When upgrading to version 2022.2 or later, you need to manually specify the new location for the migrated data.

> **Note: Important**
> Make sure that before the procedure, you have a backup of your data.

1. To access the Datalore container, run the following command:

```
kubectl exec -it datalore-0 -c datalore -- bash
```

2. To rename the data directories in the new version:

```
mv /opt/data/webdav /opt/data/web-dav
mv /opt/data/blobs /opt/data/blob
```

> **Tip:**
> You only need to specify the new location for one such upgrade. This procedure will not be required when upgrading from version 2022.2 and later.

## Earlier versions

Perform the steps in the collapsed section to upgrade from version 0.3.0.

Procedure: Upgrade from version 0.3.0

1. [Update Hub](update-hub.html) if your Datalore installation uses it.

2. Execute the following command to stop traffic to Datalore:

```
kubectl delete svc datalore-on-premise
```

3. Wait for approximately one minute until the running computations are stopped. Then, execute the following command:

```
kubectl exec -it datalore-on-premise-0 -c postgres -- psql -ddatalore -Uadmin -c 'delete from core."RunningComputationsData";'
```

4. Delete the Docker Hub token:

```
kubectl delete secret regcred
```

5. Continue the procedure as described below.

Procedure: Upgrade to version 2021.3.5

1. Delete Datalore:

```
kubectl delete -k ./datalore
```

> **Tip:**
> If you upgrade from 0.3.0, ignore the following message:
>
>
>
>
> ```
> Error from server (NotFound): error when deleting "datalore/": services "datalore-on-premise" not found
> ```

2. Clone the `datalore-configs` repository.

3. Check out the 2021.1.3.5 branch.

4. Update Hub:

1. Copy the `spec.template.spec.volumes` values from the old `hub/statefulSet.yaml` file into the new one (in the new branch).

> **Note:**
> This is a very important step for preserving your data.

2. Update `statefulset`:

```
kubectl apply -k hub/
```

3. Get the Hub token and copy it:

```
kubectl logs service/hub
```

4. Open Hub at HUB_ROOT_URL, specify the token, and click login and, in the next window, upgrade.

5. Update Datalore:

1. Copy `datalore/configs/volumes_config.yaml` from the old directory to the new one.

> **Note:**
> This is a very important step for preserving your data.

2. Copy `datalore/configs/plans_config.yaml` to the new directory.

3. If the agent configuration was changed, copy the `datalore/configs/agents_config.yaml` to the new directory and change the `image:` field to the respective tag.

4. If you used custom environments, copy `datalore/configs/envs` too.

5. Copy the `ROOT_PASSWORD` value from `datalore/configs/db_config.yaml` to `datalore/configs/db_secret_env.txt`.

Pay attention to the difference in format:

* Old file: ```YAML apiVersion: v1 kind: ConfigMap metadata: name: datalore-on-premise-db-env data: ROOT_PASSWORD: "changeme" ```

* New file: ```YAML ROOT_PASSWORD=changeme ```

6. Copy the variables from `datalore/configs/user_config.yaml` to `datalore/configs/user_secret_env.sh`.

Pay attention to the difference in format:

* Old file: ```YAML apiVersion: v1 kind: ConfigMap metadata: name: datalore-on-premise-env data: FRONTEND_URL: "http://datalore.example.com" HUB_PUBLIC_BASE_URL: "http://hub.datalore.example.com/hub" ... ```

* New file: ```YAML export FRONTEND_URL="http://datalore.example.com" export HUB_PUBLIC_BASE_URL="http://hub.datalore.example.com/hub" ... ```

> **Note:**
> * If you have `HUB_INTERNAL_BASE_URL="http://hub:8080/hub"` in `datalore/configs/user_config.yaml`, you can remove the parameter. If it has a different value, copy it to `user_secret_env.sh` too.
>
> * Remove `PASSWORD_SECRET` if the file contains it.

6. Launch Datalore:

```
kubectl apply -k datalore/
```

## Helm chart and Datalore version mapping

Below is the table that matches Helm chart, Hub, and Datalore versions.

| Datalore | Chart | Hub |
| --- | --- | --- |
| 2026.3 | 0.2.45 | 2026.2.52442 |
| 2026.2.4 | 0.2.44 | 2026.2.52154 |
| 2026.2.3 | 0.2.43 | 2026.2.52154 |
| 2026.2.2 | 0.2.42 | 2026.1.13570 |
| 2026.2.1 | 0.2.41 | 2026.1.13570 |
| 2026.1.1 | 0.2.39 | 2025.3.124603 |
| 2026.1 | 0.2.38 | 2025.3.124603 |
| 2025.6.2 | 0.2.37 | 2025.3.119807 |
| 2025.6.1 | 0.2.36 | 2025.3.104432 |
| 2025.6 | 0.2.35 | 2025.3.104432 |
| 2025.5.1 | 0.2.34 | 2025.2.97298 |
| 2025.5 | 0.2.33 | 2025.2.97298 |
| 2025.4.1 | 0.2.32 | 2025.1.82518 |
| 2025.4 | 0.2.31 | 2025.1.82518 |
| 2025.3.1 | 0.2.30 | 2025.1.74704 |
| 2025.2 | 0.2.28 | 2025.1.62967 |
| 2025.1 | 0.2.26 | 2024.3.56671 |
| 2024.5.1 | 0.2.25 | 2024.3.47197 |
| 2024.5 | 0.2.24 | 2024.3.47197 |
| 2024.4.1 | 0.2.23 | 2024.2.37269 |
| 2024.4 | 0.2.22 | 2024.2.37269 |
| 2024.3 | 0.2.21 | 2023.3.22912 |
| 2024.2.3 | 0.2.20 | 2023.3.22912 |
| 2024.2.2 | 0.2.19 | 2023.3.22912 |
| 2024.2.1 | 0.2.18 | 2023.3.22912 |
| 2024.2 | 0.2.17 | 2023.3.22912 |
| 2024.1 | 0.2.16 | 2023.3.22912 |
| 2023.6 | 0.2.14 | 2023.2.18873 |
| 2023.5.1 | 0.2.13 | 2023.2.18873 |
| 2023.5 | 0.2.12 | 2023.2.18873 |
| 2023.4 | 0.2.11 | 2022.3.15573 |
| 2023.3.1 | 0.2.10 | 2022.3.15573 |
| 2023.3 | 0.2.9 | 2022.3.15573 |
| 2023.2 | 0.2.8 | 2022.2.15039 |
| 2023.1 | 0.2.7 | 2022.2.15039 |
| 2022.3.1 | 0.2.6 | 2022.2.15039 |
| 2022.3 | 0.2.5 | 2022.2.15039 |
| 2022.2.3 | 0.2.4 | 2022.2.15039 |
| 2022.2.2 | 0.2.3 | 2021.1.14194 |
| 2022.2.1 | 0.2.2 | 2021.1.14194 |
| 2022.2 | 0.2.1 | 2021.1.14194 |
| 2022.1.1 | 0.2.0 | 2021.1.14194 |
| 2021.3 | 0.1.0 | 2021.1.13553 |