Building Cost Visibility For Your Kubernetes Clusters
summary
Kubernetes costs don’t appear on cloud bills so calculate them from pod resource allocations: tools read the API, multiply CPU/memory requests by unit prices, and roll up pod → namespace → cluster. Commercials like CloudHealth/Cloudability charge ~1–3% of spend; GKE metering writes to BigQuery. Open-source options include kube-resource-report (single install, web UI) and Prometheus+gryphon (more manual). Results approximate provider billing and reveal wasted “slack.” Use 80% off spot/preemptible instances, cluster autoscaler and HPA to actually cut costs.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:30Why Cost Visibility
- 3:22Cloud Providers Dont Provide Cost Visibility
- 4:04How Kubernetes Works
- 5:35Cloud Health
- 6:27Cloudbility
- 7:18Metering
- 8:16Open Source Tools
- 9:20Coop Resource Report
- 9:50CoreOS Operating Meter
- 10:53How these tools work
- 11:23CPU Memory Requests
- 13:02CPU Memory Limits
- 15:39What do these tools provide
- 16:15How to cut costs
- 16:35Cluster Scaler
- 19:47Pot Scaler
- 21:14Spot Preemptable
- 22:00Reserve Instance
- 23:17Summary
related talks
19mBuilding Cost Visibility For Your Kubernetes Clusters
35mWhy Kubernetes Can't Get Around FinOps – Cost Management Best Pra...
25mKubernetes Ate the Budget: How We Made Cost a Platform Responsibi...
14mCut Costs, Not Performance: Implement Kubernetes Cost Optimization Strategies
33mUncover Kubernetes cost-optimization trends
34mGame Over on the Bill: Playing the Cost Tetris in Kubernetes
57mKubernetes Cloud Cost Monitoring with OpenCost & Optimization Strategies
31mMonitor Your Cloud Costs Using Open Source Tooling