OPERATOR WORKFLOWS
Start with visibility. Keep action reviewable.
Use GreenKube to inspect Kubernetes cost, energy and carbon estimates through dashboards and reporting, and to review evidence-backed recommendations and proposed changes.
Recommendations and GitOps pull requests support operator review; estimates and outcomes depend on telemetry, source coverage and configuration.
Resource requests
Investigate rightsizing with context.
Use evidence-backed recommendations to investigate resource sizing while keeping changes reviewable by the team.
Available today
Cost, energy and carbon visibility, estimates, dashboards and reporting with Prometheus/Grafana integration.
Recommendation evidence and ranking
Rank recommendations using supporting evidence and operational context.
Proposed Git change and verification
Propose supported manifest changes through GitOps pull requests and verify post-change signals.
Use telemetry and dashboards to understand workload context. Review proposed request changes through your normal process and monitor their effect with the tools your team operates.
The GitOps pull-request workflow proposes supported manifest changes for review; target support depends on the documented integration and configuration.
Cluster review
Use reports to guide an operator-led audit.
A dashboard can help frame questions about resource use and cost. It does not mean every category is detected, attributable or automatically remediated.
Review reported cost
Use cost visibility and estimates as an allocation aid. Reconcile the interpretation with your provider billing and the inputs documented for your deployment.
Check energy and carbon coverage
Review which workloads and sources are represented before treating a report as a cluster-wide baseline.
Keep remediation separate
Idle-resource detection, orphan cleanup and automated remediation are not implied by visibility. Validate each action through your existing controls.
FinOps
Add a Kubernetes view to cost conversations.
GreenKube offers cost visibility and estimates for Kubernetes, with dashboards and reporting. Attribution depends on input coverage and allocation; it should complement, not replace, provider invoices and any cost platform already in use.
Compare cost with capacity and carbon context without assuming that the lowest estimated cost is always the best operational choice. An estimated opportunity is not a realized saving.
GreenOps
Make the assumptions part of the baseline.
Carbon and energy views are modelled estimates. Record the inputs, source coverage, time period and allocation boundaries used for an interpretation; the Carbon page explains why CPU proxy, infrastructure assumptions and data quality matter.
GreenKube is not a complete corporate carbon accounting system, a direct per-pod meter or a regulatory-compliance product.
Integration scope
Check integration support.
GreenKube connects Kubernetes telemetry, cost allocation and carbon inputs to recommendations and operator-reviewed GitOps workflows.
| Integration or capability | Content status |
|---|---|
| Kubernetes deployment and context | Provides node and workload context for estimates, recommendations and allocation. |
| Prometheus and Grafana | Provides telemetry, dashboards and reporting for cost, energy and carbon views. |
| Real VPA and Karpenter connectors | Connect resource recommendations to supported VPA and Karpenter configurations. |
| GitOps PR bot and target manifests | Proposes changes for supported manifest targets as pull requests for operator review. |