Skip to main content
Starting from Kubernetes version 1.25, kubernetes.io/azure-file has been deprecated. Cognigy.AI now supports s Azure File Container Storage Interface (CSI) from version 4.64.2, which replaces the Azure File provisioner. This guide will explain the migration process from Azure File Provisioner to the Azure CSI driver.

​
Prerequisites

  • Kubernetes >= v1.21.
  • The kubectl utility is installed locally.
  • Helm v3.9+ is installed on the client host.
  • Cognigy.AI installation must be >= v4.64.2.
  • Snapshots or backups of all Azure File Persistent Volume Claims or Persistent Volumes (flow modules, functions) must be ready before the migration starts.

​
Migration Process

  1. Retain the flow-modules and functions Persistent volumes. 
    kubectl patch pv <flow-modules-pv-id> -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}'
kubectl patch pv <functions-pv-id> -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}'
  2. Enable the Azure CSI provisioner in the values.yaml file. 
    flowModules:
	persistence:
		storageClass: "flow-modules"
functions:
	persistence:
		storageClass: "functions"

storageClass:
	azure:
	file:
	flowmodules:
		enabled: true
		skuName: Premium_LRS
		lfs: false
	functions:
		enabled: true
		skuName: Premium_LRS
		lfs: false
  3. Delete the flow-modules and function StorageClass. 
    kubectl delete sc flow-modules functions
  4. Reapply the helm chart. 
    helm upgrade --namespace cognigy-ai cognigy-ai oci://cognigy.azurecr.io/helm/cognigy.ai --version HELM_CHART_VERSION --values YOUR_VALUES_FILE.yaml --create-namespace

​
Rollback Process

  1. Undo all changes made to the values.yaml file during the migration.
  2. Delete the flow-modules and function StorageClass. 
    kubectl delete sc flow-modules functions
  3. Apply the Helm chart again. 
    helm upgrade --namespace cognigy-ai cognigy-ai oci://cognigy.azurecr.io/helm/cognigy.ai --version HELM_CHART_VERSION --values YOUR_VALUES_FILE.yaml --create-namespace