Skip to content
GreenKube

GreenKube — Every recommendation. One pull request. Proven savings.

Every recommendation. One pull request. Proven savings. GreenKube is the open-source optimization loop for Kubernetes clusters run with GitOps: it gathers advice from the tools you already run, delivers the best changes as pull requests to your Argo CD or Flux repository, and measures what each merged change actually saved.

VPA, Goldilocks, KRR, cloud consoles and in-house scripts all produce lists of things to optimize. The hard part comes next:

  • Which advice should you trust? Sources use different algorithms and observation windows, and they often disagree.
  • How do you apply it safely? In a GitOps setup the cluster mirrors Git. A tool that resizes pods inside the cluster creates drift, and Argo CD or Flux either reverts it or has to be told to ignore it.
  • What did the change actually save? Most tools report potential savings. Few measure what happened after the change, and fewer tie that result to the commit that caused it.

GreenKube closes that loop.



Every change is reported in three dimensions, each with its own units and its own label (projected or measured):

Money

Allocated cost from OpenCost, a bundled price catalog (AWS, Azure, OVHcloud, Scaleway) or your own rates. The share expected to reach the bill is shown separately, with its realization factor.

CO₂e

Operational emissions (energy times grid intensity from Electricity Maps, Wattnet or regional defaults) and embodied emissions, side by side with cost on every recommendation.

Released capacity

CPU cores and memory freed, projected and measured. Never converted to money, and the honest result on a fixed-capacity or on-premises cluster where the bill only moves when a node is removed.


Git is the only write path

No admission webhooks, no in-place mutation, no ignoreDifferences drift. Every change is a pull request your team reviews, and a rollback is a pull request too.

Projected is never shown as realized

Projected, measured allocated and realized (billed) savings are separate methods, labelled everywhere, and never added together.

Fail closed, explain why

When a change cannot be automated safely, GreenKube refuses and says why, with the fix. A signal that cannot be read is reported as unavailable, never counted as a pass.

Neutral by design

Every source is a plugin of the same Source SDK, and the evidence travels with the change into the pull request. A source alone never creates a recommendation: GreenKube’s own measurement is required.


GreenKube runs in the cluster it optimizes, on-premises and on clouds: AWS, GCP, Azure, OVHcloud, Scaleway, kubeadm, k3s or bare metal. One Helm install deploys the API, the controller, an isolated renderer and PostgreSQL. There is no profile and no feature flag: discovery, previews, delivery, sync tracking and measurement activate themselves when their prerequisites appear, and the Setup page lists what is active and the fix for anything missing.


Terminal window
# The demo: the full dashboard with sample data, no cluster needed
docker run --rm -p 9000:9000 greenkube/greenkube demo --no-browser --port 9000
# Open http://localhost:9000
Terminal window
# Install in your cluster
helm repo add greenkube https://GreenKubeCloud.github.io/GreenKube && helm repo update
helm install greenkube greenkube/greenkube -n greenkube --create-namespace

You can also explore the hosted demo at demo.greenkube.cloud.


GreenKube is open source under the Apache 2.0 license. Contributions are welcome, especially new recommendation sources and support for more GitOps layouts.

Hugo Lelievre

Hugo Lelievre

Creator & Lead Developer

GitHub StarsDocker Pulls