Upgrading and Patching AKS

Upgrading and Patching AKS


Upgrades:

In general, with any upgrade/update there is always likelihood things might fail so your team need to have multiple strategies, here are few suggestions that

  1. Test upgrades on non-prod first (must)
  2. AKS Upgrade API: The in-place upgrade should ideally work (easiest), one risk here is sometimes this can fail.
  3. New Node Pool: To minimise risk creating a new node pool in the same cluster with the latest version and then draining older one can be a bit more risk-averse approach.
  4. Blue Green with Node Pool - Idea is to deploy two active node pools running workloads so instead of one node pool with all the VMs use a two-node pool dividing the same number of VMs. When it comes to upgrading you apply the in-place upgrade to first node pool and then to the second one on success. In case of failure, you can easily scale the running node pool and scale down failed one.
  5. Creating a new cluster, this is a good approach however will need to be managed carefully as it starts to have a dependency on other components like Ingress traffic, persistent volumes etc.
  6. Blue Green with AKS Cluster - This is another approach where you always have two clusters running workload when it comes to upgrading you can always upgrade one cluster at a time. ‌

    I came across interesting MS Ignite Talk with some of the approaches I discussed here


Security Patches / Reboots:

Linux

Windows

Useful AKS Resources

AKS Current preview features: https://aka.ms/aks/previewfeatures
AKS Release notes: https://aka.ms/aks/releasenotes
AKS Public roadmap: http://aka.ms/aks/roadmap
AKS Known issues: https://aka.ms/aks/knownissues


Share Tweet Send
0 Comments
Loading...