Cost Optimization 📈


Komodor’s advanced cost capabilities are offered as part of Komodor’s paid plans, including 14-day trials.
Learn more about our pricing plans, or contact us to request trial access

Komodor analyzes your cluster resources and consumption and provides 2 main capabilities:
1. Complete visibility into your Kubernetes cost allocation
2. Actionable optimization via right-sizing recommendations

When clicking on ‘Cost Optimization’, you’ll notice tabs for two different pages: 1. Cost Allocation - full visibility into your costs structure from your overall environment to specific clusters, namespaces, or services
2. Right Sizing - Detailed recommendations based on actual consumption vs. configured requests


  • An agent update is required per cluster
    • Agent version 0.2.42 and above
    • Metrics enabled
    • Update command:
      helm repo update; helm upgrade --install k8s-watcher komodorio/k8s-watcher --set metrics.enabled=true --reuse-values
    • A relevant notification will appear if the agent isn’t up-to-date
  • To generate valuable, significant analysis & recommendations, we recommend waiting at least 7 days after the agent update to review your data.

Please Note: Our calculations are based on default values for CPU & memory monthly prices. If needed, you can modify these values to fit your exact prices.

Komodor Attributes

  • Optimization Score: How optimized your environment is, using a 0%-100% range. Calculated based on current costs, the savings recommended by Komodor, and the savings already applied.
    • For example, if your current costs are $10k, and Komodor identifies a saving opportunity of 30% ($3k), your optimization score will be 70%.
  • Share of Allocated Cost: The % out of the total allocated (requested) costs associated with each row, in the selected scope and timeframe.

Cost Allocation

Kubernetes as a centralized infrastructure is usually used by multiple teams within the organization, making it complex to associate cluster-related costs to workloads, identify potential cost anomalies, etc.

Komodor’s cost allocation page provides clear visibility into your Kubernetes costs, to easily associate costs to clusters, namespaces, workloads, and services It provides a high-level understanding of the opportunities for improvement and optimization, and you can use our right-sizing page & reports to dive deeper.

When to use Cost Allocation

  • If you’d like to keep different teams, departments, or team members responsible and accountable for their unique Kubernetes costs
  • If your Kubernetes costs have significantly increased (trust us, we’ve been there!), but you’re unsure what’s the root cause

Cost Allocation Attributes

  • Total Costs: Overall costs for the scope currently reviewed
    • Limited permissions or any filters applied for either your Komodor user or this specific page can impact the numbers presented
  • Potential Saving: The $ amount you can save by applying all of our recommendations
  • Unallocated resources: Cost of resources not currently associated with any pod or resources reserved for system processes
    • Unallocated resources will be displayed as a column when grouping by cluster, or an aggregated, additional row when grouping by namespace or service git.



Sizing a micro-service requires running performance testing and constant optimization. Komodor analyzes the actual consumption against the allocated resources and provides an extensive overview of suggested modifications and savings.

Our right-sizing dashboard includes: a high-level picture of your current cost recommended cost and the potential saving
- Visualization of our recommendations against your requests during the last 30 days, for both Memory & CPU
- Detailed right sizing recommendations per service
- The table will only include services in which there is a saving potential

When to use Right Sizing

If Then
You’re looking to cut down significantly increased Kubernetes cloud costs without compromising performance Choose the perfect optimization strategy for your needs to confidently right size
You (or your teams) are unsure how to configure CPU & memory requests for your containers, or duplicate requests from existing containers Komodor cannot recommend initial requests but can offer adjusted right-sizing recommendations based on actual usage within a week

Understanding the right-sizing page

  • Our right sizing recommendations are based on the last 30 days
    • Therefore, expect to see different results vs. your cost allocation page, in which you can set different timelines
  • Your overview data can be scoped to one or more clusters (default: all)
    • However, you can apply additional filters for the detailed report at the bottom of the page by clicking on ‘Filters’ right above it
  • The right sizing report looks quite similar to the cost allocation report, but there are a few key differences:
    • This report offers a more granular default view, showing recommendations per service
    • The CPU (core) and memory (MiB) columns will include both your current status (similar to the Cost Allocation report) and the recommended new requests

Komodor’s Optimization Strategies

When making right-sizing recommendations, it’s important to understand your preferences and needs. Choose a specific optimization strategy to ensure our recommendations are based on the right balance between your costs and your resource availability.

Strategy Name Description
Conservative Prirotizies availability over cost optimization
Moderate - Recommended, default strategy A mixed, balanced strategy
Aggressive Prioritizes cost optimization over availability

Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.