Skip to content
GreenKube

Cost Optimization

GreenKube combines FinOps and GreenOps into a single platform, helping you cut both cloud costs and carbon emissions simultaneously.

Smart Detection

Section titled “Smart Detection”

GreenKube automatically analyzes your cluster to detect optimization opportunities:

🧟 Zombie Pods

Section titled “🧟 Zombie Pods”

Pods that consume resources but do little to no actual work:

  • Near-zero CPU utilization over extended periods
  • No meaningful network traffic
  • Running but not serving requests

📏 Rightsizing Opportunities

Section titled “📏 Rightsizing Opportunities”

Workloads where resource requests/limits are significantly mismatched with actual usage:

  • Over-provisioned: Requests far exceed actual usage → wasting money and energy
  • Under-provisioned: Actual usage near or above limits → risk of OOM kills and throttling

⚖️ Autoscaling Candidates

Section titled “⚖️ Autoscaling Candidates”

Workloads that would benefit from Horizontal Pod Autoscaling (HPA):

  • High variance in resource usage over time
  • Periodic traffic patterns
  • Currently running at fixed replica count

🌍 Carbon-Aware Scheduling

Section titled “🌍 Carbon-Aware Scheduling”

Suggestions to shift non-urgent workloads to times or regions with lower carbon intensity.

Savings Estimation

Section titled “Savings Estimation”

Each recommendation includes an estimated annual impact:

MetricDescription
Annual cost savingsProjected $ reduction per year
Annual CO₂e savingsProjected gCO₂e reduction per year
Priorityhigh, medium, or low

Recommendation Lifecycle & Savings Tracking

Section titled “Recommendation Lifecycle & Savings Tracking”

Once you act on a recommendation, you can mark it as applied via the API. GreenKube then records realized savings and attributes them to actual collection periods through the savings ledger, driving Prometheus gauges:

  • greenkube_co2e_savings_attributed_grams_total
  • greenkube_cost_savings_attributed_dollars_total

These appear in the Grafana Impact Command Center and on the dashboard summary.

How to Use

Section titled “How to Use”

Via Dashboard

Section titled “Via Dashboard”

Navigate to the /recommendations page to see current active recommendations, ignored recommendations, realized savings, and estimated annual savings. The current UI exposes ignore and restore actions; applying a recommendation is currently done through the API.

Via CLI

Section titled “Via CLI”
Terminal window
greenkube recommend
# CI/CD gate: exit 1 if recommendations found
greenkube recommend --fail-on-recommendations

Via API

Section titled “Via API”
Terminal window
GET /api/v1/recommendations/active
GET /api/v1/recommendations/applied
GET /api/v1/recommendations/savings
PATCH /api/v1/recommendations/{id}/apply
DELETE /api/v1/recommendations/{id}/ignore

Via API

Section titled “Via API”
Terminal window
curl http://localhost:8000/api/v1/recommendations

Integration with OpenCost

Section titled “Integration with OpenCost”

GreenKube integrates with OpenCost to provide accurate cost data:

  • Actual cloud pricing (on-demand, spot, reserved)
  • Per-pod cost allocation
  • Namespace-level cost breakdown
Section titled “Related”