Skip to content
GreenKube

Carbon Tracking

GreenKube’s carbon tracking converts your Kubernetes cluster’s energy consumption into CO₂ equivalent emissions using real-time electricity grid carbon intensity data.

The EU’s Corporate Sustainability Reporting Directive (CSRD) requires companies to disclose the carbon footprint of their entire value chain — including cloud infrastructure (Scope 3). Most organizations have no visibility into the emissions generated by their Kubernetes workloads.

GreenKube estimates the power consumption of each pod using a combination of:

  • CPU utilization × node TDP (Thermal Design Power)
  • Memory utilization × per-GB power coefficient
  • GPU utilization × GPU TDP (when applicable)
  • Network and disk I/O power overhead

Each node is automatically mapped to a carbon zone based on its cloud provider and region. GreenKube includes built-in mappings for:

  • AWS (all regions)
  • Google Cloud Platform (all regions)
  • Microsoft Azure (all regions)
  • OVH Cloud
  • Scaleway

GreenKube fetches real-time carbon intensity (gCO₂/kWh) from Electricity Maps for each carbon zone. This means your emissions tracking reflects the actual energy mix of the grid powering your workloads.

CO₂e (grams) = Energy (kWh) × Carbon Intensity (gCO₂/kWh)

This is computed per pod, aggregated per namespace, and rolled up to the cluster level.

GreenKube helps you meet ESRS E1 (Climate Change) disclosure requirements by providing:

RequirementGreenKube Feature
Scope 3 emissions (cloud)Per-pod CO₂e calculation
Historical dataTime-series storage with configurable retention
Audit trailImmutable metric snapshots with timestamps
Reporting formatsCSV, JSON export; API access
Methodology transparencyOpen-source estimation models

To enable real-time carbon intensity, set your Electricity Maps API token:

# Helm values.yaml
electricityMaps:
enabled: true
token: "your-api-token"

Without a token, GreenKube falls back to static carbon intensity averages per country — still useful, but less accurate.