New to Kestra?
Use blueprints to kickstart your first workflows.
Detects Azure Kubernetes Service (AKS) node pools reaching maximum autoscale capacity ceiling to prevent pod scheduling starvation.
This workflow audits Azure Kubernetes Service (AKS) clusters by querying node pool configurations through the Azure CLI container (az aks nodepool list). When Kubernetes deployments experience organic traffic growth or bursty batch jobs, the cluster autoscaler expands node count up to the configured maxCount ceiling. Once this limit is reached, the autoscaler cannot provision further VM instances, leading to Pending pods, container scheduling starvation, and degraded service SLAs. The workflow identifies saturated pools and immediately dispatches alerts.
maxCount before business workloads suffer.Azure Kubernetes Service Cluster User Role and Reader permissions.AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID, and SLACK_WEBHOOK configured in Kestra.maxCount via az aks nodepool update upon platform team Slack approval.