Is a redudant cluster needed to avoid downtime when upgrading AKS cluster?

Martin Edwin Schjødt Nielsen 26 Reputation points

I have been told by a consultant that there is no way to upgrade a AKS cluster without downtime, and we therefore
would need a redundant cluster to avoid downtime. To me that sounds odd. Can anyone confirm whether that is
correct or not?

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,343 questions
0 comments No comments
{count} vote

Accepted answer
  1. Supratim Sircar 181 Reputation points

    A redundant cluster is not required but you can use the max-surge setting to create new buffer nodes when some nodes are upgrading.

    For example, a cluster that has 5 node pools, each with a count of 4 nodes, has a total of 20 nodes. If each node pool has a max surge value of 50%, additional compute and IP quota of 10 nodes (2 nodes * 5 pools) is required to complete the upgrade.

    The max surge setting on a node pool is permanent. Subsequent Kubernetes upgrades or node version upgrades will use this setting. You may change the max surge value for your node pools at any time. For production node pools, Microsoft recommends a max-surge setting of 33%.

    # Set max surge for a new node pool
    az aks nodepool add -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster --max-surge 33%

    # Update max surge for an existing node pool
    az aks nodepool update -n mynodepool -g MyResourceGroup --cluster-name MyManagedCluster --max-surge 5


    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful