AI assistants: this page is available as Markdown at https://documentation.cluedin.net/operate/upgrade/2026-03-00.md. The index of the whole documentation, with instructions for AI assistants, is at https://documentation.cluedin.net/llms.txt.

2026.03.00

reference Facts, options, APIs

On this page

1. Prerequisites
2. Guide
   1. Stage 1: Prepare for upgrade
   2. Stage 2: Stop workloads and back up data
   3. Stage 3: Migrate infrastructure data
   4. Stage 4: Run the application upgrade
   5. Stage 5: Run Data Upgrade
   6. Stage 6: Finalize Upgrade

This document covers the upgrade process from 2026.02.00 to 2026.03.00. This upgrade includes RabbitMQ configuration and data migration, and Elasticsearch index migration.

We do not support upgrading directly to this version from prior to 2026.02.00.

Prerequisites

• Access to the Helm chart version 3.0.0. You may need to run helm repo update to grab the latest version.
• kubectl
• Helm
• platform-upgrade-v3-stage1.yml values.
• platform-upgrade-v3-stage2.yml values.
• A single-node Elasticsearch deployment. The supplied migration scripts do not support multi-node clusters; contact CluedIn support for a separate migration procedure.

Guide

Before any upgrade takes place, ensure you have taken a snapshot or backup of all your running PVCs in your AKS cluster and the Azure SQL databases. This is very important as databases will be upgraded during this process.

Stage 1: Prepare for upgrade

1. Connect to your cluster using the kubeconfig.

2. Export your current Helm values file. Keep one copy for the upgrade process and another as a backup.

3. In the values file, update the following properties:

    global:
      image:
        tag: "2026.03.00"
      strategy:
        type: Recreate
   
    application:
      cluedin:
        components:
          packages:
          - name: "CluedIn.Connector.FileStorage.All.500"
            version: "100.0.0"
          - name: "CluedIn.Connector.AzureDedicatedSqlPool.500"
            version: "100.0.0"
          - name: "CluedIn.Connector.AzureEventHub.500"
            version: "100.0.0"
          - name: "CluedIn.Connector.AzureServiceBus.500"
            version: "100.0.0"
          - name: "CluedIn.Connector.Dataverse.500"
            version: "100.0.0"
          - name: "CluedIn.Connector.Dataverse.V2.502" 
            version: "100.0.0"
          - name: "CluedIn.Connector.Http.500"
            version: "100.0.0"
          - name: "CluedIn.Connector.Snowflake.500"
            version: "100.0.0"
          - name: "CluedIn.Connector.SqlServer.500"
            version: "100.0.0"
          - name: "CluedIn.EnterpriseFlows.PowerAutomate.500"
            version: "100.0.0"
          - name: "CluedIn.ExternalSearch.Providers.DuckDuckGo.Provider.500"
            version: "100.0.0"
          - name: "CluedIn.ExternalSearch.Providers.PermId.Provider.500"
            version: "100.0.0"
          - name: "CluedIn.ExternalSearch.Providers.Web.500"
            version: "100.0.0"
          - name: "CluedIn.PowerApps.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.Bregg.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.ClearBit.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.CompanyHouse.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.CVR.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.Gleif.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.GoogleImages.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.GoogleMaps.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.KnowledgeGraph.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.Libpostal.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.OpenCorporates.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.Providers.ArtificialIntelligence.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.Providers.AzureOpenAI.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.Providers.BvD.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.Providers.VatLayer.500"
            version: "100.0.0"
          - name: "CluedIn.Provider.ExternalSearch.RestApi.500"
            version: "100.0.0"
          - name: "CluedIn.Purview.500"
            version: "100.0.0"
   
   

4. Update the RabbitMQ section in your values file. Remove auth.existingPasswordSecret, auth.existingErlangSecret, extraVolumeMounts using /opt/bitnami/rabbitmq and extraVolumes, as shown below:

    infrastructure:
    rabbitmq:
       persistence:
          size: <VOLUME_SIZE>
       resources:
          limits:
          cpu: "<CPU_LIMITS>"
          memory: <MEMORY_LIMITS>
          requests:
          cpu: "<CPU_REQUESTS>"
          memory: <MEMORY_REQUESTS>
   

   Keep your existing global.keyvault.secretProviderClasses.cluedin-rabbitmq configuration if you are using Key Vault.

Stage 2: Stop workloads and back up data

1. Apply the stage 1 upgrade values file 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 3.0.0 \
        --values ${CustomValues} \
        --values platform-upgrade-v3-stage1.yml \
        --wait \
        --timeout 10m0s
   

Apply the stage values file last so that it overrides your custom values.

1. Check the pods. Wait until all CluedIn application pods have stopped.

2. Take a backup before continuing. Confirm the backup completed successfully.

The next stage deletes original Elasticsearch 7.x indices after reindexing and verification. This cannot be reversed through a Helm rollback; a pre-migration data backup is required for recovery.

Stage 3: Migrate infrastructure data

1. Apply the stage 2 upgrade values file 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 3.0.0 \
        --values ${CustomValues} \
        --values platform-upgrade-v3-stage2.yml \
        --wait \
        --timeout 30m0s
   

Apply the stage values file last so that it overrides your custom values.

❗ The time required depends on the amount of data. The timeout shown is an example; allow sufficient time for your environment. A Helm timeout alone does not mean the migration has stopped or completed.

1. Monitor the migration logs in elasticsearch:

    kubectl get pods -n cluedin
    kubectl logs cluedin-elasticsearch-0 -n cluedin -c cluedin-upgrade-es8
    kubectl logs cluedin-elasticsearch-0 -n cluedin -c cluedin-upgrade-es9
   

2. Wait until the deployment finishes.

3. Perform the validation:

   • Confirm Elasticsearch is Ready and both init containers completed successfully.
   • Confirm RabbitMQ is healthy and its existing data was retained.
   • Review migration logs for failures. Application pods remain stopped during this stage.

If there are any issues during the upgrade process, please do not hesitate to reach out to CluedIn support.

Stage 4: Run the application upgrade

1. Apply your custom values without either upgrade stage files:

    # ${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 3.0.0 \
        --values ${CustomValues} \
        --set application.system.upgradeMode=true \
        --set application.system.runDatabaseJobsOnUpgrade=true \
        --set application.system.runNugetFullRestore=true \
        --wait \
        --timeout 10m0s
   

   After a few minutes, it should complete successfully.

2. Wait until the deployment finishes.

3. 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.

Stage 5: Run Data Upgrade

1. Apply data upgrade by running following command:

    # ${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 3.0.0 \
       --values "${CustomValues}" \
       --set application.system.upgradeMode=true \
       --set application.bootstrap.dataUpgrade.toVersion=Version500 \
       --wait \
       --timeout 30m0s
   

2. Monitor the server pod logs for the data upgrade progress.

3. Validation:

   • ❗ Confirm the data upgrade completed successfully and its resource reached Active state.

Stage 6: Finalize Upgrade

1. Run the final stage of the upgrade to bring the system back online (disable upgrade mode):

    # ${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 3.0.0 \
      --values ${CustomValues} \
      --set application.system.upgradeMode=false \
      --set application.system.runDatabaseJobsOnUpgrade=false \
      --set application.system.runNugetFullRestore=false \
      --wait \
      --timeout 30m0s
   

2. Validation:

   • Ensure no errors in the pod logs.
   • Verify the server starts in normal mode.
   • Ensure cluedin-ui pod is Running.

If there are any issues during the upgrade process, please do not hesitate to reach out to CluedIn support.