AKS Node Pool Autoscaler Not Enabled
The pool is fixed, so pods stay pending under load and idle nodes are paid for at quiet times.
Free to start. No card. The playground just needs your work email.
AzureKubernetes
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable cluster autoscaler on AKS node pool.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- AKS Agent Pools on Azure
- The fix, by hand
- Open Portal → Kubernetes services → ‹cluster› → Node pools → the resource → Scale node pool.
- Select Autoscale. Set Min node count to your steady-state baseline (typical: max(2, replica-floor of system workloads)).
- Set Max node count to the peak burst you're willing to pay for. Don't leave it unbounded.
- Apply. Watch the Cluster autoscaler events (kubectl describe configmap cluster-autoscaler-status) for the first day.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1356- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.