This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 75%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJV%3C/text%3E%3C/svg%3E)
According to the MS documentation, the az aks upgrade command is used to perform an update for an AKS cluster with zero downtime. The command takes care of updating each cluster node with the most recent changes. I'm using my biceps code to push the AKS upgrade. Does it get better? and is it KubernetesVersion,OrchestratorVersion are the only parameters configurations to handle AKS cluster Upgrade while using Biceps? or else we need to consider auto-upgrade? What are the finest procedures for upgrading an AKS Cluster while having Biceps as a medium, please?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 35%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Hello @Jijo Varghese-FT ,
Welcome to Microsoft QnA & apologies for the delay in response.
Yes, you are right. KubernetesVersion and OrchestratorVersion are the only parameters (as far as I know and researched) to handle AKS cluster upgrades while using Bicep.
You can also use auto-upgrade feature to minimize the overhead of manual upgrades and save time and operational costs.
You can find more details here:
auto-upgrade-cluster
Please feel free to reach back to me if you have any questions (do tag me in your response). Thanks.
Hello @Jijo Varghese-FT ,
Welcome to Microsoft QnA & apologies for the delay in response.
Yes, you are right. KubernetesVersion and OrchestratorVersion are the only parameters (as far as I know and researched) to handle AKS cluster upgrades while using Bicep.
You can also use auto-upgrade feature to minimize the overhead of manual upgrades and save time and operational costs.
You can find more details here:
auto-upgrade-cluster
Please feel free to reach back to me if you have any questions (do tag me in your response). Thanks.