# Orphaned and Overprovisioned Resources in AKS Clusters

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-and-overprovisioned-resources-in-aks-clusters

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

# Orphaned and Overprovisioned Resources in AKS Clusters

## Explanation

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 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.

## Relevant Billing Model

While the AKS control plane is free, costs 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.

## Detection

- 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

## Remediation

- 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

## Relevant Documentation

- https://learn.microsoft.com/en-us/azure/aks/

- https://learn.microsoft.com/en-us/azure/aks/concepts-storage

- https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-overview

[Submit Feedback](https://hub.pointfive.co/inefficiencies/orphaned-and-overprovisioned-resources-in-aks-clusters)

## At a glance

Reference

CER-0100

Cloud provider

Azure

Service

Azure AKS

Category

[Compute](https://www.pointfive.co/efficiency-hub/service-category/compute)

Inefficiency type

Inefficient Configuration

## Contributed by

- ### Yisrael Gross

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.