2024.12.01

On this page

1. Prerequisites
2. Guide

This document covers the upgrade process from 2024.12 to 2024.12.01.

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

Prerequisites

• Access to the helm chart version 2.4.1. You may need to helm repo update to grab the latest.
• kubectl and 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.

1. Connect to your cluster via the kubeconfig.
2. Export your current running helm values file. Keep one for this process, and also keep one as a backup.

3. In the values file we’ll be working with, update the following properties:

    global:
      image:
        tag: "2024.12.01"
      strategy:
        type: Recreate
   
    application:
      cluedin:
        image:
          tag: "2024.12.01"
        components:
          packages:
          - name: "CluedIn.Connector.AzureEventHub"
            version: "4.0.1"
          - name: "CluedIn.Connector.Dataverse"
            version: "4.4.0"
          - name: "CluedIn.Connector.Http"
            version: "4.0.0"
          - name: "CluedIn.DataVerse"
            version: "4.2.2"
          - name: "CluedIn.EventHub"
            version: "4.4.0"
          - name: "CluedIn.Vocabularies.CommonDataModel"
            version: "4.4.0"
          - name: "CluedIn.Connector.AzureDataLake"
            version: "4.4.1"
          - name: "CluedIn.Connector.AzureDedicatedSqlPool"
            version: "4.0.2"
          - name: "CluedIn.Connector.AzureServiceBus"
            version: "4.0.2"
          - name: "CluedIn.Connector.OneLake"
            version: "4.4.1"
          - name: "CluedIn.ExternalSearch.Providers.DuckDuckGo.Provider"
            version: "4.4.0"
          - name: "CluedIn.ExternalSearch.Providers.PermId.Provider"
            version: "4.4.0"
          - name: "CluedIn.ExternalSearch.Providers.Web"
            version: "4.4.0"
          - name: "CluedIn.Provider.ExternalSearch.Bregg"
            version: "4.4.0"
          - name: "CluedIn.Provider.ExternalSearch.ClearBit"
            version: "4.4.0"
          - name: "CluedIn.Provider.ExternalSearch.CompanyHouse"
            version: "4.4.0"
          - name: "CluedIn.Provider.ExternalSearch.CVR"
            version: "4.4.0"
          - name: "CluedIn.Provider.ExternalSearch.Gleif"
            version: "4.4.0"
          - name: "CluedIn.Provider.ExternalSearch.GoogleMaps"
            version: "4.4.0"
          - name: "CluedIn.Provider.ExternalSearch.KnowledgeGraph"
            version: "4.4.0"
          - name: "CluedIn.Provider.ExternalSearch.Libpostal"
            version: "4.4.0"
          - name: "CluedIn.Provider.ExternalSearch.OpenCorporates"
            version: "4.4.0"
          - name: "CluedIn.Provider.ExternalSearch.Providers.VatLayer"
            version: "4.4.0"
          - name: "CluedIn.Purview"
            version: "4.4.0"
          - name: "CluedIn.PowerApps"
            version: "4.4.0"
          - name: "CluedIn.EnterpriseFlows.PowerAutomate"
            version: "4.4.0"
          - name: "CluedIn.Connector.SqlServer"
            version: "4.1.2"
   

4. Delete existing node exporter daemonsets

    kubectl delete daemonsets/cluedin-prometheus-node-exporter -n cluedin
   

5. Delete existing prometheus CRDS.

    kubectl delete crd alertmanagerconfigs.monitoring.coreos.com
    kubectl delete crd alertmanagers.monitoring.coreos.com
    kubectl delete crd podmonitors.monitoring.coreos.com
    kubectl delete crd probes.monitoring.coreos.com
    kubectl delete crd prometheusagents.monitoring.coreos.com
    kubectl delete crd prometheuses.monitoring.coreos.com
    kubectl delete crd prometheusrules.monitoring.coreos.com
    kubectl delete crd scrapeconfigs.monitoring.coreos.com
    kubectl delete crd servicemonitors.monitoring.coreos.com
    kubectl delete crd thanosrulers.monitoring.coreos.com 
   

6. Redeploy prometheus CRDS with compatible version for the new helm chart.

   kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.79.0/example/prometheus-operator-crd/monitoring.coreos.com_alertmanagerconfigs.yaml
   kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.79.0/example/prometheus-operator-crd/monitoring.coreos.com_alertmanagers.yaml
   kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.79.0/example/prometheus-operator-crd/monitoring.coreos.com_podmonitors.yaml
   kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.79.0/example/prometheus-operator-crd/monitoring.coreos.com_probes.yaml
   kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.79.0/example/prometheus-operator-crd/monitoring.coreos.com_prometheusagents.yaml
   kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.79.0/example/prometheus-operator-crd/monitoring.coreos.com_prometheuses.yaml
   kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.79.0/example/prometheus-operator-crd/monitoring.coreos.com_prometheusrules.yaml
   kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.79.0/example/prometheus-operator-crd/monitoring.coreos.com_scrapeconfigs.yaml
   kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.79.0/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml
   kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.79.0/example/prometheus-operator-crd/monitoring.coreos.com_thanosrulers.yaml
   

7. 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.4.1 \
        --values ${CustomValues} \
        --wait \
        --timeout 10m0s
   

   After a few minutes, it should successfully complete.

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