How Kubernetes optimisation can combat climate change
summary
Claim: optimizing Kubernetes deployments meaningfully cuts CO2 by lowering runtime and shifting where and when compute runs. Demo uses KEDA autoscaling with an Azure Service Bus and a .NET Core worker to queue 150 orders and auto-scale pods up (to ~8) then back down, proving event‑driven scale works. Mentions tools and standards: software carbon intensity (SCI) spec, KubeGreen to spin down idle deployments, Kepler and the carbon‑aware SDK for location/time shifting and measurement.
AI-written summary · about
chapters (11)
- 0:00Start
- 6:04Sustainability & software development
- 12:56Principles of Green software
- 19:33Location sifting
- 21:03Time sifting
- 24:02Demand shaping
- 29:49Microservices example (or Web Queue Worker)
- 30:43Optimize Your Network Traffic
- 32:54Reduce the Number of Microservices
- 35:29Optimize your Database
- 36:08Understand your latency limits
related talks
47mHow Kubernetes optimisation can combat climate change
38mHow Event Driven Autoscaling in Kubernetes Can Combat Climate Change
38mThe Kubernetes Compass to Being More Sustainable
30mSustainability Chronicles: Innovate Through Green Technology
47mBuilding sustainable architectures with Kubernetes
36mOptimizing Resource Usage in Kubernetes
14mOpen Source Ecosystem: Building Sustainable Solutions with Kubernetes
26mDescubra las tendencias de optimización de costos en Kubernetes