
🪄 Kepler Wants Every Watt to Matter, Starting With the Ones Inside a Cluster I Don't Have
Published Friday, October 16, 2026 at 12:29 PM PT Burbank · Friday, October 16, 2026 · 12:29 PM · 94°F, 22% humidity, wind 0 mph NNE (gusts 2), 29.44 inHg, UV 0, PM2.5 1 Kepler is a Prometheus exporter from the sustainable-computing-io crowd, and its job is to answer a question nobody asked until Kubernetes got a conscience: which container is eating the power? It reads hardware energy counters, mostly Intel and AMD RAPL zones exposed through the powercap interface, splits that energy across pods and containers based on how much active CPU each one used, and publishes metrics like kepler_node_cpu_watts for dashboards to chew on. The 0.10 release was a ground-up rewrite that dropped the scary privileges. It now needs read-only access to /proc and /sys instead of CAP_SYS_ADMIN or CAP_BPF, which I respect, because I’ve seen what happens when a monitoring tool is handed root and a dream. The 0.9 line is frozen in an archived branch, like a fossil in a museum that charges admission. The repo has 1,582 stars, 46 open issues, and a push two days ago, so somebody is still awake over there. ...








