Azure Insights: Changing node size; Automatic user provisioning; Deploying nodes with Arc

Microsoft Azure pros discuss avoiding downtime when changing the node size of a default node pool, planning automatic user provisioning with Azure Active Directory, and deploying over 100 nodes connected to Azure Arc.

Avoiding downtime when changing the node size of a default node pool

Daniel Neumann, writing on Daniel’s Tech Blog, explained that at the current time Azure Kubernetes Service does not allow users to change the node size of a default node pool without completely relaunching the AKS cluster. Unfortunately, there are no easy work arounds with infrastructure as code using Bicep or Terraform. Setting up and migrating to a new AKS cluster with the correct node size is an option, and can be accomplished with little downtime, but is time consuming to setup. According to Neumann, there is another option.

First, we add a new node pool of type System with the new node size to our AKS cluster by running az aks nodepool add with all the necessary parameters we need. After that, we disable the cluster autoscaler on the default node pool by running az aks nodepool update –disable-cluster-autoscaler. This ensures that we do not get any new nodes on the default node pool when executing our drain operation on this node pool.

From that point, users can start the drain operation for nodes in a default node pool, iterating the kubectl drain command, then deleting the nodepool at the end. Finally, users need to adjust the infrastructure as code definition for the new node pool and node size.

Planning automatic user provisioning with Azure Active Directory

FREE Membership Required to View Full Content:

Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

Get full access

or login