Should an SRE Care About FinOps? Using Observability to...
summary
Company runs FinOps POV on AWS with Kubernetes using Kubecost and other open source tools and reports 35% cost savings across clusters by applying specific actions: right-size container requests, remove underutilized nodes, and set real‑time alerts. Environment scale is large with 2,200 K8s in production and 5,000+ AWS accounts, so savings require culture change, tagging and account strategy, and some legacy problems still limit further reductions despite clear operational wins.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:27Bank’s cloud migration
- 2:57What is FinOps
- 4:45FinOps phases and activities
- 6:32FinOps teams and responsibilities
- 7:40KU Cost platform overview
- 9:10Demo: cost-saving recommendations
- 10:40Why care about FinOps
- 11:41Building FinOps culture
related talks
45mFinOps for Kubernetes: Monitoring Spend with OpenCost
24mFinOps for Observability: Optimizing OpenSearch Costs Without Sacrificing Visibility
36mFinOps & Observability: technical implementation
43mWhere SRE Can Go Wrong
13mManaging Multi-Cloud Complexity
42mDemystifying SRE and DevOps
54mUnraveling the Differences
34mOptimizing operations & container management