# FinOps: Holding engineering teams accountable for spend Page: https://stenobird.com/podcast/adventures-in-devops/finops-holding-engineering-teams-accountable-for-spend Text version: https://stenobird.com/podcast/adventures-in-devops/finops-holding-engineering-teams-accountable-for-spend.md Podcast: [Adventures in DevOps](https://stenobird.com/podcast/adventures-in-devops) Published: 2025-07-31T11:17:50+00:00 Episode link: https://adventuresindevops.com/episodes/2025/07/31/finops-cost-optimization-devops-kubernetes Audio file: https://dts.podtrac.com/redirect.mp3/api.spreaker.com/download/episode/67199809/finops_cost_optimization_devops_kubernetes.mp3 Processing state: processed JSON: https://stenobird.com/v1/public/podcasts/adventures-in-devops/episodes/finops-holding-engineering-teams-accountable-for-spend Duration seconds: 3307 ## Resource Bridging the gap between engineering efficiency and financial accountability requires more than just visibility; it requires aligning incentives. This episode explores how FinOps uses automation and observability to prevent cloud waste in Kubernetes and AI workloads. ## Highlights - Main idea: FinOps is about creating a shared language between finance and engineering to drive accountability - Practical takeaway: Use Horizontal and Vertical Pod Autoscalers (HPA/VPA) alongside continuous policy enforcement to prevent resource drift - Failure mode: Relying on 'shame back' reporting instead of providing engineers with actionable, automated tooling and visibility - Main idea: The rise of AI/ML workloads is shifting the focus from managing software engineering salaries to managing massive GPU and hardware costs - Practical takeaway: Implement lightweight agents to scrape metrics rather than heavy daemon sets to minimize the 'tax' on cluster resources ## Topics FinOps, Kubernetes, Cloud Cost Management, AI Infrastructure, GPU Optimization, DevOps, Cloud Computing, Resource Scaling ## Chapters - 1:00 — The Challenge of FinOps: An introduction to the friction between financial analysts and engineering teams and the goal of bringing them together. - 5:20 — Kubernetes Cost Visibility: Discussing the difficulty of mapping pod-level resource usage to node-level billing and the impact on cloud spend. - 13:20 — Automating Resource Optimization: The necessity of continuous policies to handle applications that change their resource requirements frequently. - 21:30 — FinOps in the Age of AI: How Spark jobs, data workloads, and the increasing cost of GPUs are making cost optimization a critical priority. - 25:50 — Standardizing Cloud Data: Using the FOCUS spec to create a unified abstraction layer across AWS, Azure, and GCP for better cost allocation. - 30:00 — Efficient Metric Collection: A look at using lightweight agents instead of daemon sets to monitor cluster metrics without bloating resource usage. - 46:40 — The Hardware-Software Symbiosis: Reflecting on the 'Red Queen's race' and why AI innovation may require fundamental shifts in hardware architecture. ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/adventures-in-devops/episodes/finops-holding-engineering-teams-accountable-for-spend/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/adventures-in-devops/finops-holding-engineering-teams-accountable-for-spend.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.