Update AKS Node Pool Scale

Overview

The Update AKS Node Pool Scale Action is used to update the minCount and maxCount for Node Pools in an Azure Kubernetes Service (AKS) Managed Cluster.

This dynamic scaling approach allows for efficient resource management and cost reduction. Additionally, it allows for easy restoration of previous scale settings, simplifying resource management in response to evolving operational demands.

Save on the cost of unutilized resources while ensuring your AKS Cluster is optimally scaled for your team's needs.

Important to Note

The Update AKS Node Pool Scale action can target Node Pools in AKS Clusters that satisfy all of these qualities:

• The targeted AKS cluster has multiple node pools
• Node pools have the enableAutoScaling property set to true
• Node pools are of type VirtualMachineScaleSets

Action Configuration

Tag Groups

One or many Tag Groups used to filter AKS Clusters by their tags.

Choice Between Parameters

Min Count

The minCount parameter to apply to each scalable node pool of the AKS Cluster.

Max Count

The maxCount parameter to apply to each scalable node pool of the AKS Cluster.

Or

Restore to Previous Scale

Every time the action runs and GorillaStack makes a change to a targeted node pool, it will remember it's previous scale.

This allows GorillaStack users to utilize the Restore to Previous Scale option, retrieving the remembered Min Count and Max Count values and applying these settings for each targeted node pool.

Typically Min Count and Max Count parameters are used to scale down AKS clusters at the end of a business day and the Restore to Previous Scale option is utilized in a corresponding rule responsible for bringing the AKS cluster back up to scale at the start of a work day.