> ## Documentation Index > Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Why This Isnt Just SkyLine Airs Problem > Explains FinOps practices and automation to detect, attribute, assign ownership, and remediate cloud resource waste across teams to improve cost transparency and accountability. Before we unpack the FinOps framework, let's zoom out: SkyLine Air isn't a one-off worst-case story — it reflects a common industry situation. Surveys from the [FinOps community](https://www.finops.org) show that only a small minority of teams have a formal chargeback or showback model. In practice, this means many organizations lack clear accountability for cloud waste — for example, idle or over-provisioned `pods` running in Kubernetes — and therefore lack a consistent process to remediate it. That lack of ownership is precisely why we adopt FinOps practices and build automation like the AI agent: to automatically detect waste, attribute costs, assign ownership, and guide teams to corrective actions. In short, we address an industry-wide problem many teams face when operating in the cloud. * Detection: identify idle or oversized resources (compute, storage, networking). * Attribution: map cost back to the teams or services responsible. * Assignment: create ownership and responsibility for remediation. * Remediation: provide automated or prescriptive fixes (rightsizing, scheduling, deleting). * Verification: track outcomes and feedback into budgeting and forecasts. | Resource Type | Typical Waste | Example Remediation | | - | - | - | | `pods` (Kubernetes) | Idle or over-provisioned containers | Rightsize resource requests/limits, autoscale, terminate idle pods | | Virtual Machines | Oversized instances or forgotten VMs | Change instance type, use spot/preemptible instances, schedule shutdowns | | Storage | Unattached or infrequently accessed volumes | Delete unused volumes, move to cheaper tiers, lifecycle policies | | Networking | Unused NAT gateways, idle load balancers | Remove unused endpoints, reduce provisioned throughput | The term "chargeback" (or "showback") refers to allocating cloud costs back to the teams or business units that incurred them so those teams can be accountable for their spending and waste. Why this matters for product and engineering leaders: * Cost transparency helps prioritize technical debt and operational improvements. * Clear ownership reduces friction and accelerates remediation. * Automated detection and remediation scale better than manual processes. Links and references * [FinOps Foundation — FinOps community](https://www.finops.org) * [Kubernetes Documentation — Concepts: Pods](https://kubernetes.io/docs/concepts/workloads/pods/) * [Cloud Cost Management guides and best practices](https://www.google.com/search?q=cloud+cost+management+best+practices) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.