Git is the only write path
No admission webhooks, no in-place mutation, no drift. Every change, including a rollback, is a pull request.
GreenKube is an open-source optimization loop for Kubernetes clusters run with GitOps. It collects optimization recommendations from the tools you already run, ranks them by value and risk, delivers the best ones as reviewable pull requests to your GitOps repository, and then measures what each merged change actually saved: in money, in CO₂e, and in released capacity (CPU cores and memory freed).
sources ─► recommendation ─► plan (diff + digest) ─► pull request ─► merge ▲ │ │ Argo CD / Flux sync │ │ ledger ◄── measurement vs counterfactual ◄── apply detection ◄─────────┘Teams running Kubernetes do not lack optimization advice. The hard part comes after the advice:
ignoreDifferences.| Stage | What GreenKube does |
|---|---|
| Aggregate | Starts from GreenKube’s own measurements and reads the other sources of advice in your cluster (VPA and Goldilocks, Robusta KRR reports and anything sent to the push API) into one signal model, provenance kept. |
| Decide | GreenKube’s measured value decides each size; the other sources raise the confidence when they agree and lower it when they disagree (one vote per engine, contested advice labelled and never approved automatically). A source alone never creates a recommendation. Each recommendation carries evidence, a projected impact, a risk level, a confidence score and a risk-adjusted expected value. |
| Deliver | Finds the workload’s Git source through Argo CD or Flux, renders the change in an isolated sandbox, and opens a pull request on GitHub, GitLab or Gitea once a signed-in user approves the exact diff (its digest). |
| Verify | Waits for Argo CD or Flux to sync the merged revision, then detects that the new configuration is live. |
| Measure | Compares the workload after the change with a counterfactual built from the 7 days before it, with a 90% confidence interval, confounder checks and health gates, and compares the result with the projection. |
| Record | Writes every outcome to an append-only, hash-chained ledger linked to the pull request, merge commit, synced revision and measurement. |
Git is the only write path
No admission webhooks, no in-place mutation, no drift. Every change, including a rollback, is a pull request.
Projected is never realized
Projected, measured allocated and realized (billed) savings are labelled and never added together. Released capacity is never converted to money.
Fail closed, explain why
When a change cannot be automated safely, GreenKube refuses and tells you why and what would fix it.
Evidence travels with the change
The pull request carries the usage evidence, impact, risk, rendered diff and what will be verified after the merge.
It runs in the cluster it optimizes, on-premises and on clouds (AWS, GCP, Azure, OVHcloud, Scaleway, kubeadm, k3s, bare metal).
kubectl steps and measures the change once you mark it applied.