Scale Node Pool
A 3-step recipe with Azure Kubernetes Service. We can help you get access.
Recipe · 3 steps
Scale Node Pool
with Azure Kubernetes Service · IT Infrastructure Management
Change the node count of an AKS agent pool and wait for the scale to finish.
- Read the agent pool to capture its current node count and VM size before changing the count.
- Submit a create-or-update setting the new count under the ARM properties object. A 200 indicates the scale request was accepted.
- Read the agent pool and inspect provisioningState. While it is still Scaling the flow loops back to this step; once it reports Succeeded the workflow ends.
What you'll need to have ready
- subscriptionId: The ID of the target subscription (valid UUID).
- resourceGroupName: The name of the resource group.
- resourceName: The name of the managed cluster.
- agentPoolName: The name of the agent pool to scale.
- newNodeCount: The desired number of nodes after scaling.
- apiVersion: The AKS REST API version to use.
- accessToken: An Azure AD bearer token with user_impersonation scope.
For your developer
Arazzo workflow microsoft-azure-kubernetes-service:scale-node-pool, 3 operations: AgentPools_Get → AgentPools_CreateOrUpdate → AgentPools_Get. Specs on APIs.io.