---
title: 2024.07.03
url: https://documentation.cluedin.net/operate/upgrade/2024-07-03
content_type: reference
section: Deploy & operate > Upgrade
---

# 2024.07.03

> reference: Facts, options, APIs.

This document covers the upgrade process from 2024.07 to 2024.07.03.

> **Important:** We do not support upgrading directly to this version from prior to 2024.02.

## Prerequisites
- Access to the helm chart version `2.3.2`. You may need to `helm repo update` to grab the latest.
- `kubectl` and `helm`

## Guide

> **Important:** 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.
1. Export your current running helm values file. Keep one for this process, and also keep one as a backup.
1. In the values file we'll be working with, update the following properties:

    ```yaml
    global:
      image:
        tag: "2024.07.03"
      strategy:
        type: Recreate

    application:
      bootstrap:
        dataUpgrade:
          toVersion: 'Version430'

      cluedin:
        components:
          packages:
          - name: CluedIn.Connector.AzureDataLake
            version: 4.3.0
          - name: CluedIn.Connector.Dataverse
            version: 4.3.0
          - name: CluedIn.EventHub
            version: 4.3.0
          - name: CluedIn.PowerApps
            version: 4.3.0
          - name: CluedIn.Provider.ExternalSearch.ClearBit
            version: 4.1.0
          - name: CluedIn.Provider.ExternalSearch.CVR
            version: 4.1.0
          - name: CluedIn.Provider.ExternalSearch.GoogleMaps
            version: 4.1.0
          - name: CluedIn.Provider.ExternalSearch.Libpostal
            version: 4.1.2
          - name: CluedIn.Purview
            version: 4.3.0
          - name: CluedIn.Vocabularies.CommonDataModel
            version: 4.3.0
          - name: CluedIn.Connector.SqlServer
            version: 4.1.0
          - name: CluedIn.ExternalSearch.Providers.Web
            version: 4.1.0
          - name: CluedIn.Connector.OneLake
            version: 4.3.0

      roles:
        main:
          resources:
            limits:
              memory: 2G

      datasourceProcessing:
        replicas: 2
        resources:
          requests:
            cpu: 1000m
            memory: 512M
          limits:
            cpu: 2000m
            memory: 8G

      datasource:
        resources:
          requests:
            cpu: 500m
            memory: 512M
          limits:
            cpu: 500m
            memory: 512M

      submitter:
        resources:
          requests:
            memory: 1G
          limits:
            memory: 1G

      gql:
        resources:
          requests:
            memory: 512M
          limits:
            memory: 4G

      ui:
        resources:
          requests:
            memory: 256M

      monitoring:
        alertManager:
          licenseKey: <your-license-key>

    infrastructure:
      haproxy-ingress:
        controller:
          resources:
            requests:
              cpu: 125m
            limits:
              cpu: 500m

      cert-manager:
        cainjector:
          resources:
            requests:
              memory: 128Mi
    ```

1. Delete existing node exporter daemonsets

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

1. 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 
    ```
1.  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.71.0/example/prometheus-operator-crd/monitoring.coreos.com_alertmanagerconfigs.yaml
    kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.71.0/example/prometheus-operator-crd/monitoring.coreos.com_alertmanagers.yaml
    kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.71.0/example/prometheus-operator-crd/monitoring.coreos.com_podmonitors.yaml
    kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.71.0/example/prometheus-operator-crd/monitoring.coreos.com_probes.yaml
    kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.71.0/example/prometheus-operator-crd/monitoring.coreos.com_prometheusagents.yaml
    kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.71.0/example/prometheus-operator-crd/monitoring.coreos.com_prometheuses.yaml
    kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.71.0/example/prometheus-operator-crd/monitoring.coreos.com_prometheusrules.yaml
    kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.71.0/example/prometheus-operator-crd/monitoring.coreos.com_scrapeconfigs.yaml
    kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.71.0/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml
    kubectl apply --server-side -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/v0.71.0/example/prometheus-operator-crd/monitoring.coreos.com_thanosrulers.yaml
    ```

1. Apply the values file from your shell by running the following:

    ```bash
    # ${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.3.2 \
        --reuse-values \
        --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.

Up: [Upgrade](https://documentation.cluedin.net/operate/upgrade.md)