2026.01.00 Support
On this page
This document covers the upgrade process for 2026.01.00 to its support update.
We do not support upgrading directly to this version from prior to 2026.01.00.
Prerequisites
- Access to the Helm chart version
2.7.0. You may need to runhelm repo updateto grab the latest version. - kubectl
- Helm
Guide
Before any upgrade takes place, ensure you have taken a snapshot or backup of all your running PVCs in your AKS cluster. This is very important as databases may be upgraded during this process.
Stage 1: Apply values for support release
-
Connect to your cluster using the kubeconfig.
-
Export your current Helm values file. Keep one copy for the upgrade process and another as a backup.
-
In the values file, update the following properties:
application: datasourceProcessing: image: tag: 4.7.0-update.118 datasource: image: tag: 4.7.0-update.118 submitter: image: tag: 4.7.0-update.118 gql: image: tag: 4.7.0-update.32 ui: image: tag: 4.7.0-update.98 infrastructure: neo4J: image: tag: 4.7.0-update.3 global: containerImages: initSql: image: tag: 4.7.0-update.3 initNeo4J: image: tag: 4.7.0-update.3 -
Apply the values file from your shell by running the following:
# ${CustomValues} refers to the values file you have amended with the above changes. Please type the full path here. helm upgrade cluedin-platform -n cluedin cluedin/cluedin-platform \ --version 2.7.0 \ --values ${CustomValues} \ --set application.system.runDatabaseJobsOnUpgrade=true \ --set application.system.runNugetFullRestore=true \ --wait \ --timeout 10m0sAfter a few minutes, it should complete successfully.
-
Wait until the deployment finishes.
-
Perform the validation:
-
Make sure that all pods are healthy and all jobs are completed.
-
Ensure that there are no errors in the pod logs.
-
If there are any issues during the upgrade process, please do not hesitate to reach out to CluedIn support.