Which of your hundred pods is burning the power?
Node-level power tells you a cluster is expensive, not which service to fix. In shared clusters, one team's workload hides inside everyone's bill.
The Kepler project measures the energy of each pod in a Kubernetes cluster. GreenCode's research review looks at tools like this.
GreenCode helps tackle this by tracing energy and CO2e to the services that cause it, including services running hot and services barely running at all. It mines a running estate and rebuilds it as infrastructure as code. More on this.
Which of your hundred pods is burning the power? The power meter on a machine tells you the cluster is expensive. It does not tell you which service to fix. In a shared cluster, one team's workload hides inside everyone's bill. Here is the fix you can use today. First, add an energy exporter that reports each pod. Tools like Kepler and Scaphandre report energy per pod, container and process. Send it to the dashboards you already use. Next, rank namespaces and services by energy per request. For a clean benchmark, pin the workload to a machine of its own. Now the cluster bill becomes a list of services to improve. The Kepler project measures the energy of each pod in a Kubernetes cluster. GreenCode's research review looks at tools like this. GreenCode helps tackle this by tracing energy and carbon to the services that cause it. It maps your running systems and rebuilds them as code. That was GreenCode Tech Tip number forty-nine. Follow for the next tip, and find more on greencode.ai/tech-tips.
Share this
