
Measure, understand, and reduce the carbon footprint of your Kubernetes infrastructure.
GreenKube is an open-source FinGreenOps platform for Kubernetes. It gives DevOps, SRE, and FinOps teams workload-level carbon visibility and cost control — without complex setup or expensive SaaS tooling.
Live demo: demo.greenkube.cloud — explore the full dashboard with realistic sample data, no install required.
| Grafana dashboard |
|---|
![]() |
| Dashboard | Automation & GitOps |
|---|---|
![]() |
![]() |
| Recommendations | Nodes |
|---|---|
![]() |
![]() |
| Report | Settings |
|---|---|
![]() |
![]() |
| Document | Description |
|---|---|
| Installation guide | Step-by-step Helm installation, values, development vs production, API keys, and frontend access |
| Architecture | Technical architecture, data flow, and component breakdown |
| Power estimation methodology | How energy and CO₂e are calculated |
| Configuration | All Helm values and environment variables |
| API Reference | REST API endpoints, parameters, and examples |
| CLI Reference | greenkube start, demo, and other CLI commands |
| Recommendation lifecycle | How recommendations are generated, persisted, actioned, and measured |
| GitOps automation | Git discovery, plan lifecycle, pull requests, rollback, and security model |
| Local Minikube deployments | Development and production-like local deployments |
| Prometheus & Grafana | ServiceMonitor setup and Grafana dashboard import |
| Observability and SLOs | Control-loop metrics, objectives, and alert examples |
| Sustainability score | How the 0–100 composite score is computed |
| Changelog | Version history |
Published dashboard on Grafana.com: https://grafana.com/grafana/dashboards/25377-greenkube-fingreenops-dashboard/
The recommended deployment method is the official Helm chart. See the Installation guide for the full walkthrough, including production secrets, external databases, GitOps automation, and ingress setup.
helm repo add greenkube https://GreenKubeCloud.github.io/GreenKube
helm repo update
helm install greenkube greenkube/greenkube \
-n greenkube \
--create-namespace
The chart defaults to the standalone profile, production authentication, a generated API key, and disabled GitOps automation. Retrieve the key from the release Secret:
kubectl -n greenkube get secret greenkube \
-o jsonpath='{.data.GREENKUBE_API_KEY}' | base64 -d
Once deployed, access the dashboard and API from the same origin:
kubectl -n greenkube port-forward svc/greenkube-api 8000:8000
# Open http://localhost:8000 and paste the API key when prompted
The browser keeps the key in memory only and asks for it again after a reload.
| Profile | Components | Recommended for |
|---|---|---|
standalone |
Collector and API in one Deployment; inline automation when enabled | Evaluations, small clusters, local installations |
production |
Separate API, controller, and optional automation worker Deployments; migration Job; leader election | Production clusters and horizontally scaled API deployments |
For production, create the API key and database credentials in a Kubernetes Secret and reference it with secrets.existingSecret instead of storing them in a values file. Start from helm-chart/values-production.yaml. See Production mode.
Create a my-values.yaml to customise your deployment:
config:
clusterName: prod-eu-west
cloudProvider: aws
defaultZone: FR # Fallback Electricity Maps zone
prometheus:
url: "" # Leave empty for automatic in-cluster discovery
queryRangeStep: 5m
opencost:
url: ""
secrets:
# Electricity Maps API token for real-time grid carbon intensity.
# Free token: https://www.electricitymaps.com/
electricityMapsToken: ""
Apply it:
helm upgrade --install greenkube greenkube/greenkube \
-n greenkube \
-f my-values.yaml
For the full list of variables, see the Configuration reference.
GreenKube auto-discovers the following services. No manual configuration is required in most cases.
| Service | Purpose | Required? |
|---|---|---|
| Prometheus | CPU, memory, network, disk metrics, and restart counts | Strongly recommended |
| Metrics Server | Per-container CPU/memory evidence and verification | Recommended |
| OpenCost | Cost allocation data | Optional |
| Electricity Maps or Wattnet | Grid carbon intensity | Optional |
| Argo CD / Flux | GitOps automation | Optional |
Cloud providers expose zone labels on nodes automatically. On bare-metal clusters, label your nodes manually:
kubectl label nodes --all topology.kubernetes.io/zone=FR
Then set config.cloudProvider: on-prem and config.defaultZone: FR in your values. See the Configuration reference for details.
Automation is opt-in and fails closed when it cannot prove a safe target. It requires a supported GitOps source, a Git provider token stored in a Kubernetes Secret, a repository allowlist, and a renderer boundary enforced by your CNI.
See GitOps automation for setup, provider configuration, supported source layouts, webhooks, policy gates, rollback, and limitations.
docker run --rm -p 9000:9000 greenkube/greenkube demo --no-browser --port 9000
# Open http://localhost:9000
The demo includes a two-year sample history, with hourly workload metrics in the recent window selected by --days (30 days by default) and daily metric and carbon-intensity points further back. It includes estimated emissions, costs, node history, and optimization recommendations.
Contributions are welcome. See CONTRIBUTING.md to get started.
git clone https://github.com/GreenKubeCloud/GreenKube.git
cd GreenKube
uv sync
pytest
Licensed under the Apache 2.0 License.