6 documented Azure AKS cost inefficiencies, each with how to detect it and how to fix it.
Azure AKSCER-0099
Kubernetes environments often accumulate unused resources over time as applications evolve. Common examples include Persistent Volume Claims (PVCs) backed by Azure Disks, Services that trigger load balancer provisioning, or stale...
Azure AKSCER-0100
Clusters often accumulate unused components when applications are terminated or environments are cloned. These include PVCs backed by Managed Disks, Services that still front Azure Load Balancers, and test namespaces that are no longer...
Azure AKSCER-0557
In AKS, the node VMs are what you pay for, and how many nodes a cluster needs is decided by pod resource requests, not by what pods actually use. The Kubernetes scheduler places pods according to their CPU and memory requests, and the...
Azure AKSCER-0570
AKS node pools are Virtual Machine Scale Sets, and every node is a VM that bills for as long as it exists, whether or not pods are scheduled on it. A user node pool created with a fixed node count stays sized for its peak even after pods...
Azure AKSCER-0571
Development, test and sandbox AKS clusters are usually needed only during business hours, but they are created once and left running around the clock. Outside working hours they often run nothing but system components, yet every node in...
Azure AKSCER-0572
Many AKS clusters run batch jobs, CI runners, queue consumers, rendering and dev or test services on regular pay-as-you-go node pools, even though these workloads can tolerate a node disappearing. AKS supports Spot node pools backed by...
