Question 251948 in Azure Question posted in
The official documentation to get you started can be found here.

Azure – potential risks in upgrading AKS 1.21 to 1.25

we want to upgrade AKS from 1.21 to 1.25 as 1.25 is the supported version in AKS right now and AKS does not allow version to upgraded like EKS one minor version at a time.

what are the potential risks?

We have made sure all the deprecated APIs are not used anymore. other than what can be the risks with this big version jump.

The upgrade will be done in the 1.21 cluster not creating a new one. Please let me know in your experience.

Tags:

2

Answers


  1. 0

    As per MsDoc currently 1.21 is deprecated and the current version available in AKS is 1.25 so using that I am showing you the version upgrade from 1.25 to 1.27, you can apply this same logic for 1.21 to 1.25.

    az aks get-upgrades --resource-group <RgName> --name <clusterName> --output table

    enter image description here

    By default, Kubernetes uses a semantic versioning i.e. major then minor then patch so with that logic 1.25.6 -> 1.25.11 -> 1.26.3 -> 1.27.1In AKS, upgrading from 1.21 to 1.25 in a single jump is not recommended.

    In my Aks environment I am upgrading 1.25.6 -> 1.25.11 like below:

    enter image description here

    enter image description here

    Now, 1.25 to 1.26

    enter image description here

    enter image description here

    Now 1.26.3 to 1.27.1:

    enter image description here

    Finally, you can verify the same using kubectl cmd:

     kubectl get nodes -o wide

    enter image description here

    This is the safe way to upgrade your Kubernetes version in AKS if you directly jump from 1.21 to 1,25, it may cause below issues-

    • There may be breaking changes and compatibility issues could cause your applications to fail or could have performance regressions.
    Login or Signup to reply.
  2. 0

    Two recommendations:

    1. Check all your add-ons and extensions for breaking changes as well

    2. Try out the upgrade in a staging environment first. If anything breaks after the upgrade, you can’t downgrade the existing cluster anymore.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search