Explanation
Why the waste happens and who it affects.
These include PVCs backed by Managed Disks, Services that still front Azure Load Balancers, and test namespaces that are no longer maintained. Node pools are frequently overprovisioned, especially in multi-tenant or CI environments.
The cost impact of these idle resources is magnified in organizations with many environments or without standardized cleanup routines. Since billing is resource-specific, even low-cost items like Managed Disks, load balancer rules, and frontend configurations can accumulate meaningful waste over time.
Billing model
The pricing dimensions that drive this cost.
The AKS control plane is free only on the Free tier (the Standard and Premium tiers add a per-cluster management charge), and costs also accrue from the underlying compute (VMs), storage (Managed Disks provisioned via PVCs), and networking (load balancers and public IPs from Services). Orphaned and overprovisioned resources continue to incur charges even if the corresponding workloads are no longer active.
How to detect
8 checks to find it in your estate.
- Scan for unused PVCs that are not attached to any pod
- Check for abandoned StatefulSets with orphaned PVCs
- Review Services that have Azure Load Balancers but no active endpoints
- Check node pools for sustained underutilization
- Identify stale namespaces or test environments with no recent changes
- Look for config maps or secrets that are unused but still consuming control plane capacity
- Audit for Helm or CI/CD jobs that left behind residual resources
- Scan for unused Ingress controllers that may still have associated Azure Application Gateways or Load Balancers
How to fix
7 ways to remove the waste.
- Delete unused PVCs to release backing Managed Disks
- Clean up Services that are no longer in use to avoid unnecessary load balancer charges
- Scale down underutilized node pools
- Remove outdated or inactive namespaces
- Implement periodic cleanup routines for ephemeral environments
- Implement resource tagging strategies to track the environment lifecycle
- Use Azure Policy to enforce cleanup requirements
Documentation
Vendor references for pricing and configuration.
- https://learn.microsoft.com/en-us/azure/aks/Reference
- https://learn.microsoft.com/en-us/azure/aks/concepts-storageReference
- https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-overviewReference