AZURE Kubernetes Service (AKS) upgrade minor version from 1.32.3 to 1.33.7
In this article, we shall discuss the folloing topic “AZURE Kubernetes Service (AKS) upgrade minor version from 1.32.3 to 1.33.7”. Updating a managed Kubernetes environment is rarely just a routine maintenance task. It is a critical operation that directly affects the platform’s stability, security, and the availability of its features. Please, see How to protect Azure Kubernetes Service (AKS) with Azure Backup, and How to use Container Insights for Azure Kubernetes Workload.
In the context of Azure Kubernetes Service (AKS). Even a minor version update, such as the move from version 1.32.3 to 1.33.7. This requires careful planning, testing and execution. Before proceeding with the AKS cluster update, consult your DevOps team responsible for developing applications and microservices to verify the backward compatibility of the version to be updated. In general, upgrading to a minor release should not significantly impact applications running on AKS.
This article explores the end-to-end process of performing a minor version update in AKS, highlighting not only the technical steps involved. But, also the operational considerations that engineers must take into account.
AZURE Kubernetes Service Upgrade Guidance
Although Azure abstracts much of the complexity of the control plane. The responsibility for workload compatibility, node pool management and deployment continuity still falls on the operator.
We will examine key aspects such as version skew policies, pre-update checks, node image updates, and potential breaking changes introduced between these Kubernetes releases. Furthermore, the article will provide practical guidance on how to minimise downtime. Verify the cluster’s health after the update, and leverage native Azure tools to simplify the process.
Whether maintaining production clusters or managing development environments. Understanding the nuances of AKS version updates is essential to ensuring reliability and taking full advantage of the continuous evolution of Kubernetes.
Please see Unspecified GSS failure: How to fix Clock skew too great, how to get the Windows 10 Version 22H2 Update, and how to create and monitor Apps using the Azure Kubernetes Service manifest.
AKS Upgrade
Select the AKS cluster; it is best to start with the test or pre-production cluster.
Select the version you wish to update and click ‘Check’ e click Save
Once you have clicked “Save”, the upgrade process begins
Go to ‘Notifications’ to check the upgrade process logs so you can keep an eye on it
Activity log: monitor the process
Activity log: monitor the process
Notification that the upgrade has been successfully completed
Check the current version of AKS post upgrade
Fix Upgrade blocked Due to Unsatisfied Pod Disruption Budget (PDBs). During the upgrade process, you may encounter this type of error.
The update cannot proceed because the ALLOWED DISRUPTIONS parameter in the default namespace is set to 0, whereas it must be at least 1 in order to proceed.
Run this command to check
az aks command invoke --resource-group YOUR-Resource-Group --name ClusterName --command "kubectl get pdb -n default"
Update the `maxUnavailable` parameter from 0 to 1 in the default namespace.
Try the upgrade again; it should work without the error that caused you to abort it previously
I hope you found this blogpost on “AZURE Kubernetes Service (AKS) upgrade minor version from 1.32.3 to 1.33.7” very useful. Please feel free to leave a comment below.
