gopaddle User Guide
  • 👋Welcome to gopaddle
  • Overview
    • 💡Getting Started
    • Register a Cluster
      • Register Rancher Prime - RKE2
      • Register K3S
      • Register MicroK8s
      • Register Kind
      • Register minikube
      • Register Kubeadm Cluster
      • Register AWS EKS Cluster
        • EKS Cluster with public or public/private access point
        • EKS Cluster with private access endpoint and a bastion host
        • Validate Cluster Connectivity
      • Register Azure AKS Cluster
      • Register Google GKE Cluster
      • Register Huawei Cloud Container Engine
    • Register GitHub Account
    • Register Jira Account
    • Register ChatGPT Assistant
    • 💻Kubernetes IDE
      • Filters
      • Editor
      • Flat vs Tree View
      • Developer Tools
    • 🙋AI Assistant
      • Chat with AI
      • Raise a Jira Ticket from Chat Window
      • Create Runbook from Chat Window
    • 📖Runbook Hub
      • Create Runbook Hub
      • Attach Runbook Hub to Cluster
      • Enhancing contents of Runbooks with AI
      • Detach Runbook Hub from Cluster
      • Syncing Runbook Hub with GitHub
      • Delete Runbook / Runbook Hub
    • ⏱️Installing Community Edition
      • MicroK8s Addon
        • On Ubuntu
        • On MacOS
      • Docker Desktop
      • SUSE Rancher Prime
      • Digital Ocean
      • Akamai Linode
      • Kind Cluster
      • Helm
      • Docker Compose
      • Accessing gopaddle UI
    • 📈Improving performance of resource discovery
    • Provision new Cluster
      • Register Cloud Account
        • AWS
          • Quickstart AWS Setup
          • IAM Access Policies
          • AWS Setup Script
        • Azure
          • Create Azure Application
          • Register Azure Cloud Authenticator
          • Register Azure Account
        • Google
      • Provision Clusters on Cloud
        • AWS EKS
          • AWS EKS Reference Architecture
          • Adding an AWS IAM Role (EKS Master / Node Pool)
          • Public EKS Cluster
          • All Private EKS Cluster (beta)
          • Creating a Node Pool
        • Azure AKS
          • Creating a Node Pool
          • Enable Public IP Node Access for Azure Deployments
          • VMSS Autoscaling Rules
        • Google GKE
          • Creating a Node Pool
  • 🔎Troubleshooting
    • Cluster Resource View Issues
      • Network Error ! ServerError: Response not successful: Received status code 503
      • Network Error ! TypeError: Failed to fetch
      • Network Error ! ServerParseError: Unexpected token 'j', "json: erro"... is not valid JSON
      • Updating Labels and Annotations does not get reflected in resources list
      • Filtered resources are not fully listed
    • Runbook Issues
      • Deleting a runbook from .gp.yaml does not detach annotation in resources
      • Deleting a Code Account from gopaddle UI does not detach annotation in resources
    • Jira Issues
      • Creating, Updating or Appending a Jira issue fails with error INVALID_INPUT
    • EKS Issues
    • Deployment Issues
    • Node Issues
    • Huawei Issues
Powered by GitBook
On this page
  • Pre-requisite:
  • Adding autoscaling rules to Azure node pool
  1. Overview
  2. Provision new Cluster
  3. Provision Clusters on Cloud
  4. Azure AKS

VMSS Autoscaling Rules

PreviousEnable Public IP Node Access for Azure DeploymentsNextGoogle GKE

Last updated 1 year ago

Azure Autoscaling rules can be attached to an Azure Node pool to dynamically scale up or down the nodes within the nodepool.

Pre-requisite:

  1. In order to use the Azure Autoscaling rules, enable the microsoft.insights in the Azure Subscription.

  2. Login to your Azure account.

  3. Choose the Subscription and Under Resource Providers search for microsoft.insights and enable it.

Adding autoscaling rules to Azure node pool

While creating the cluster via gopaddle or while adding a node pool to the cluster via gopaddle, you can set the scaling rules for the node pool.

Metric defines the attribute to be monitored. Scaling can be performed based on the below mentioned metrics.

  1. Percentage CPU

  2. Network In

  3. Network Out

  4. Disk Read Bytes

  5. Disk Write Bytes

  6. Disk Read Operations/Sec

  7. Disk Write Operations/Sec

  8. CPU Credits Remaining

  9. CPU Credits Consumed

Measure specifies the measure of the metrics to be watched for. Measure can be one of the blow:

  1. Average

  2. Minimum

  3. Maximum

  4. Total

  5. Last

  6. Count

'When' specifies the operator. It can be :

Capacity specifies the value of the metric.

  • >=

  • <

  • <=

  • =

  • !=

Scale specifies whether to increase or decrease the node count in the node pool.

Scale by specifies the number of nodes to increase or decrease.

Scale Type specifies the behaviour once the scaling condition matches. It can be

  1. ChangeCount: Increase or decrease the number of nodes

  2. ExactCount: Maintain a specified number of nodes

  3. PertcentChangeCount: Increase or decrease the number of nodes by a percentage of the current nodes.

Watch Duration is the duration to watche the change in metric before triggering an autoscaling event.

Cooldown Period is the duration to wait before triggering the subsequent autoscaling event.

Time Window is the sampling duratin and is used to normalize the metrics collected. Say aggregate the data every 1 minute.

Statistic specifies the aggregation method for the time window. It can be :

  1. Average

  2. Min

  3. Max

  4. Sum

For more information on Azure Virtual Machine Scaling Set (VMSS), please check the document .

here
Page cover image
Azure VMSS Scaling Rules in gopaddle