# Orphaned Kubernetes resources in AKS | Cloud Efficiency Hub Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-kubernetes-resources-230dd Kubernetes environments often accumulate unused resources over time as applications evolve. By: Yonah Dissen Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Orphaned Kubernetes Resources in AKS The short version Kubernetes environments often accumulate unused resources over time as applications evolve. Yonah Dissen Azure service [Azure AKS](https://www.pointfive.co/efficiency-hub/cloud-services/azure-aks) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0099 Type Idle or Unused Resource ## Explanation Why the waste happens and who it affects. Common examples include Persistent Volume Claims (PVCs) backed by Azure Disks, Services that trigger load balancer provisioning, or stale ConfigMaps and Secrets. When the associated deployments or pods are removed, these resources may remain unless explicitly deleted. In AKS, this can lead to unmanaged costs, such as idle managed disks from orphaned PVCs or public load balancers from Services of type LoadBalancer. Even lightweight resources like unused Secrets or ConfigMaps degrade cluster hygiene and can introduce security or operational risk. This inefficiency is common across Kubernetes environments and is scoped here to AKS. ## Billing model The pricing dimensions that drive this cost. While AKS clusters on the Free tier do not charge for the control plane (the Standard and Premium tiers add a charge for cluster management), costs arise from the underlying compute (VMs or node pools), storage (e.g., managed disks from PVCs), and networking (e.g., public IPs and load balancers from Services). Orphaned Kubernetes objects - such as PVCs, Services, ConfigMaps, and Secrets-may persist beyond the lifecycle of the workloads that created them, causing unnecessary consumption of Azure resources and cost. ## How to detect 10 checks to find it in your estate. - Review Kubernetes objects not linked to active Deployments, StatefulSets, or running Pods - Check across all namespaces, not just default (default should never be deleted - Check for PVCs not mounted by any current workload - kubectl get pvc --all-namespaces to check PVC usage - Identify Services of type LoadBalancer that are not backed by any endpoints - kubectl get svc -o wide to identify LoadBalancer services - Confirm whether any retained Services have public IPs or Azure Load Balancers associated - Locate Secrets and ConfigMaps with old creation dates and no recent usage - Validate that no Jobs or CronJobs are expected to recreate workloads using these resources - kubectl get secrets,configmaps --show-labels for unused resources ## How to fix 5 ways to remove the waste. - Before deletion, verify resources are truly orphaned - Delete orphaned PVCs to release Azure Managed Disks - Remove Services that no longer front active workloads to deallocate Load Balancers and public IPs - Clean up unreferenced ConfigMaps and Secrets - Use scheduled audits or automation tools to identify and clean up orphaned resources regularly ## Documentation Vendor references for pricing and configuration. - [Concepts - Storage in Azure Kubernetes Service (AKS) - Azure Kubernetes Service learn.microsoft.com](https://learn.microsoft.com/en-us/azure/aks/concepts-storage) - [Use a Public Standard Load Balancer in Azure Kubernetes Service (AKS) - Azure Kubernetes Service learn.microsoft.com](https://learn.microsoft.com/en-us/azure/aks/load-balancer-standard) - [Azure Kubernetes Service (AKS) Free, Standard, and Premium Pricing Tiers - Azure Kubernetes Service learn.microsoft.com](https://learn.microsoft.com/en-us/azure/aks/free-standard-pricing-tiers) - [Pricing - Azure Kubernetes Service (AKS) azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/kubernetes-service/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure AKS CER-0100 ### [Orphaned and Overprovisioned Resources in AKS Clusters](https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-and-overprovisioned-resources-in-aks-clusters) 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... Compute - Azure AKS CER-0557 ### [Overprovisioned Pod Resource Requests in AKS](https://www.pointfive.co/efficiency-hub/inefficiencies/overprovisioned-pod-resource-requests-in-aks) 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... Compute - Azure AKS CER-0570 ### [AKS Node Pools Without Cluster Autoscaler or With a Slow Scale-Down Profile](https://www.pointfive.co/efficiency-hub/inefficiencies/aks-node-pools-without-cluster-autoscaler-or-with-a-slow-scale-down-profile) 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... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.