Platform · Kubernetes
EKS node groups, cluster debris, and the fee traps K8s doesn't warn you about.
Kubernetes creates its own category of AWS waste — orphaned volumes, zombie load balancers, and version-driven fee traps. CloudPivot extends the same detect-and-execute model to the cluster layer.
The cluster ledger
Namespace-level cost, and the fee trap K8s won't warn you about.
Split-cost allocation shows which namespace is actually driving cluster spend — not just which cluster is expensive. Version fee-traps get flagged before AWS's Extended Support multiplies the control-plane fee up to 6×, and the debris deleted services leave behind is found with a price attached.
Node groups on the same weekend schedule
Off-hours scheduling extends to EKS node groups, not just EC2 and RDS — the scheduler core reaches Kubernetes-managed capacity too.
Clean up the debris Kubernetes leaves behind
Orphaned persistent volumes and zombie load balancers from deleted services get found and flagged for cleanup.
Pod-level guidance, honestly labeled
Pod-layer recommendations are advisory, not automated — CloudPivot tells you where to look without claiming to auto-tune your workloads.
See what your clusters are costing outside the pod spec.
The Kubernetes scan checks node groups, orphaned resources, and version fee traps — free, config-only.