OPEN-SOURCE KUBERNETES OPTIMIZATION

Kubernetes optimization, from evidence to pull request.

GreenKube is an open-source, self-hosted project for understanding Kubernetes cost, energy and carbon, with recommendations and GitOps workflows that keep operators in control.

Review evidence, propose supported manifest changes, and compare expected impact with observed outcomes before deciding what to apply.

Kubernetes optimization, from evidence to pull request.
  1. TelemetryReview Kubernetes cost, energy and carbon estimates through Prometheus and Grafana.
  2. Recommendation and evidenceRank recommendations with supporting evidence and clear operational context.
  3. Git diff and pull requestPropose supported manifest changes as Git diffs and pull requests for operator review.
  4. Apply and verifyVerify applied changes against post-change signals and defined health checks.
  5. Measured outcomeCompare estimated impact with observed outcomes without treating estimates as guaranteed savings.
Apache-2.0Self-hostedKubernetes-nativeBuilt in the open

The platform

Visibility first; estimates with context.

GreenKube helps teams inspect Kubernetes cost, energy and carbon estimates, review evidence-backed recommendations, and propose operator-reviewed changes.

GreenKube is Apache-2.0 licensed and designed to be self-hosted. Prometheus and Grafana bring cluster telemetry into dashboards, recommendations and reports; consult the documentation for setup and data requirements.

A displayed estimate is not a direct measurement, a cloud invoice, or a promise of savings. The result depends on available telemetry, source coverage and configuration.

Operator-reviewed workflow

A path from observation to a reviewed change.

GreenKube connects telemetry, evidence, proposed changes and post-change checks while leaving production decisions with the operator.

  1. 01

    Observe

    Use Kubernetes telemetry and Prometheus/Grafana dashboards to review cost, energy and carbon estimates.

  2. 02

    Prioritize with evidence

    Compare recommendations using their supporting evidence, confidence and operational context.

  3. 03

    Propose a Git change

    Create pull requests for supported manifest changes and let the team review them through its normal process.

  4. 04

    Check what happened

    Check applied changes and compare post-change signals with the original estimates and evidence.

Three connected operator concerns.

The platform’s views support investigation across these dimensions. They do not turn every opportunity into an automated action.

  • Cost

    Review cost visibility and reported estimates. Treat allocation as an analytical view, not an invoice or billing guarantee.

  • Energy and carbon

    Inspect energy and carbon estimates with their input coverage, source assumptions and uncertainty in mind.

  • Capacity

    Use resource context and ranked recommendations to inform operator decisions.

Integration boundary

Follow the data, not a headline number.

GreenKube integrates with Kubernetes, Prometheus and Grafana. Check the documentation for provider availability and configuration details.

release-scope.txt
              Kubernetes + Prometheus
          ↓
GreenKube cost, energy and carbon estimates
          ↓
Dashboards and reports (Grafana integration)

Evidence-backed recommendations and GitOps pull requests
          ↓
Operator review and post-change checks
            

Open source by default

Self-host the project; inspect the source.

GreenKube is open source under Apache-2.0 and is designed for self-hosting in Kubernetes. The core project is not gated behind a commercial contract.

Optional help, separate from the project.

Teams that want human support can discuss a Kubernetes optimization assessment, implementation work or ongoing review. The scope should reflect the telemetry, product capabilities and change process actually available to the team.

Services are optional. They do not unlock core software features, and the open-source project remains available without a services engagement.