> ## Documentation Index
> Fetch the complete documentation index at: https://docs.domino.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Azure Kubernetes Services (AKS) upgrade guide

<Warning>
  You must [upgrade Domino](/6.3/admin/operations/upgrade-domino) to a [compatible version of Kubernetes](/6.3/admin/architecture-and-deployment/kubernetes-infrastructure/kubernetes-compatibility) immediately after the Kubernetes upgrade. Domino will not work as expected until this is completed.

  For example, after upgrading Kubernetes to v1.22, you must upgrade to Domino v5.2 or later. Kubernetes v1.22 is not compatible with older versions of Domino. Similarly, after upgrading to Kubernetes 1.23 or 1.24, you must upgrade to Domino v5.3 or later.
</Warning>

## Prerequisites

To upgrade Kubernetes on Azure, you must have a Unix or Linux terminal with the following:

* [Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli) installed.

* [Kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/) installed.

Use environment variables to set the values of IDs, names, and labels. This simplifies the commands you’ll run when you upgrade:

```shell theme={null}
export SUB_ID=<Id of the subscription where AKS was deployed>
export RG_NAME=<Name of the resource group where AKS was deployed>
export CLUSTER_NAME=<The name of the cluster where domino is deployed>
```

## Get cluster credentials

1. If you aren’t already signed in to Azure CLI, run:

   ```shell theme={null}
   az login
   ```

2. Protect your current kubeconfig from being overwritten:

   ```shell theme={null}
   export KUBECONFIG=$(pwd)/kubeconfig
   ```

3. Get the remote kubeconfig:

   ```shell theme={null}
   az aks get-credentials --subscription $SUB_ID --resource-group $RG_NAME --name $CLUSTER_NAME -f $KUBECONFIG
   ```

## Disable the Disruption Budgets

You must temporarily disable the `PodDisruptionBudget` (PDB) for certain services. To do this, back up the PDBs, delete the original PDBs, then update Kubernetes and restore the PDBs from the backup after the update is complete.

1. Back up the PDBs:

   ```shell theme={null}
   kubectl get pdb -n domino-platform -o yaml mongodb-arbiter > mongodb-arbiter.yml
   kubectl get pdb -n domino-platform -o yaml mongodb-primary  > mongodb-primary.yml
   kubectl get pdb -n domino-platform -o yaml mongodb-secondary > mongodb-secondary.yml
   ```

2. Delete the PDBs:

   ```shell theme={null}
   kubectl delete pdb -n domino-platform mongodb-arbiter
   kubectl delete pdb -n domino-platform mongodb-primary
   kubectl delete pdb -n domino-platform mongodb-secondary
   ```

## Update the cluster

1. Check for available AKS cluster upgrades:

   ```shell theme={null}
   az aks get-upgrades --subscription $SUB_ID --resource-group $RG_NAME --name $CLUSTER_NAME --output table
   ```

2. Run the cluster update (this might take several minutes to complete):

   ```shell theme={null}
   az aks upgrade --subscription $SUB_ID --resource-group $RG_NAME --name $CLUSTER_NAME --kubernetes-version <version-number>
   ```

## Kubernetes v1.24

If you upgrade to Kubernetes 1.24, add a path annotation for the `nginx-ingress-controller` probe:

```shell theme={null}
kubectl annotate svc -n domino-platform nginx-ingress-controller "service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path=/healthz"
```

<Warning>
  You must annotate this path to avoid `504 Gateway Time-out` errors. This is because, in AKS version 1.24, the path no longer defaults to `/healthz`.
</Warning>

## Restore the disruption budgets

Run these commands from the same folder as the backup:

```shell theme={null}
kubectl apply -f mongodb-arbiter.yml
kubectl apply -f mongodb-primary.yml
kubectl apply -f mongodb-secondary.yml
```