Azure Kubernetes Services (AKS) upgrade guide

​

Prerequisites

• Azure CLI installed.
• Kubectl installed.

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:
   az login
   
2. Protect your current kubeconfig from being overwritten:
   export KUBECONFIG=$(pwd)/kubeconfig
   
3. Get the remote kubeconfig:
   az aks get-credentials --subscription $SUB_ID --resource-group $RG_NAME --name $CLUSTER_NAME -f $KUBECONFIG
   

​

Disable the disruption budgets

1. Back up the PDBs:
   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:
   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:
   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):
   az aks upgrade --subscription $SUB_ID --resource-group $RG_NAME --name $CLUSTER_NAME --kubernetes-version <version-number>
   

​

Kubernetes 1.24

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

​

Restore the disruption budgets

kubectl apply -f mongodb-arbiter.yml
kubectl apply -f mongodb-primary.yml
kubectl apply -f mongodb-secondary.yml