Skip to content
GreenKube

Multi-Cloud Support

GreenKube supports all major cloud providers out of the box, with automatic detection and region-specific carbon intensity mapping.

Supported Providers

Section titled “Supported Providers”
ProviderRegionsAuto-Detection
Amazon Web ServicesAll regions (us-east-1, eu-west-1, etc.)✅ Via node labels
Google Cloud PlatformAll regions (us-central1, europe-west1, etc.)✅ Via node labels
Microsoft AzureAll regions (eastus, westeurope, etc.)✅ Via node labels
OVH CloudAll regions (GRA, SBG, BHS, etc.)✅ Via node metadata
ScalewayAll regions (fr-par, nl-ams, pl-waw)✅ Via node metadata
On-premisesManual configurationVia config

How It Works

Section titled “How It Works”

1. Provider Detection

Section titled “1. Provider Detection”

GreenKube reads Kubernetes node labels to identify the cloud provider:

  • node.kubernetes.io/instance-type → AWS, GCP, Azure
  • topology.kubernetes.io/region → Region identifier
  • Provider-specific labels as fallback

2. Instance Profiles

Section titled “2. Instance Profiles”

Each cloud provider instance type has a profile containing:

  • CPU model and core count
  • TDP (Thermal Design Power) in watts
  • RAM capacity
  • GPU (if applicable)

These profiles are used for power estimation when Prometheus metrics aren’t granular enough.

3. Region → Carbon Zone Mapping

Section titled “3. Region → Carbon Zone Mapping”

Each cloud region is mapped to an electricity grid zone:

AWS us-east-1     → US-MIDA-PJM    (PJM Interconnection)
AWS eu-west-1     → IE              (Ireland)
GCP europe-west1  → BE              (Belgium)
Azure westeurope  → NL              (Netherlands)
OVH GRA           → FR              (France)
Scaleway fr-par   → FR              (France)

This mapping is crucial for accurate carbon tracking — a workload in eu-west-1 (Ireland, ~300 gCO₂/kWh) has a very different footprint than one in eu-north-1 (Sweden, ~20 gCO₂/kWh).

On-Premises or Unknown Providers

Section titled “On-Premises or Unknown Providers”

For on-premises clusters or unsupported providers, set:

values.yaml
config:
  cloudProvider: on-prem    # or leave as "unknown" for auto-detection
  defaultZone: "FR"         # Electricity Maps zone code
  defaults:
    pue: 1.5                # Your data center PUE

GreenKube uses the SPECpower linear model for power estimation regardless of provider.

PUE (Power Usage Effectiveness)

Section titled “PUE (Power Usage Effectiveness)”

GreenKube accounts for data center overhead using PUE ratios:

ProviderTypical PUE
AWS1.135
GCP1.10
Azure1.18
OVH1.15
On-premises (avg)1.5–2.0
Total Power = IT Power × PUE
Section titled “Related”