October 2026 release is live Read More
Breadcrumbs

K8s Savings

The K8s Savings dashboard lists specific, actionable recommendations for cutting Kubernetes cost (over-sized requests, idle workloads and nodes, and unused storage) and shows how much each one could save per month. It covers Kubernetes clusters running on any provider, whether managed (EKS, AKS, GKE) or self-managed on-prem.

Why this matters: Kubernetes cost is mostly capacity you reserve, not capacity you use: a container that requests 0.15 CPU and uses 0.03 still holds the 0.15. These recommendations find that gap and tell you exactly which request, workload, node or volume to change. On clusters you own, the saving is reserved capacity handed back, valued at the cost Mavvrik already allocates to that workload (it is not a measured drop in usage or an invoice reduction, and cash only appears when nodes are actually retired).

This shows up differently depending on your role:

  • Platform and engineering teams use the Action column as a ready-made change list: it names the exact container, workload or volume and the new value.

  • FinOps managers use the four savings widgets and the Potential Savings column to size and prioritize the opportunity.

  • Team leads filter by Cluster and Namespace to see only what their own team can act on.

Key Metrics

Four widgets at the top summarize the latest potential monthly savings:

  • Cost Savings: the total potential monthly savings across all open recommendations (the sum of the three widgets below).

  • Orphan Resources: savings from resources that are no longer attached to anything, such as persistent volumes with no claim.

  • Idle Resources: savings from workloads, nodes or GPU claims that are running but doing no useful work.

  • Rightsize Resources: savings from resources whose request or size is larger than they need.

Recommendations

The Recommendations table lists every recommendation, sorted by Potential Savings (highest first). Use the open / muted toggle to switch between recommendations that are still active and ones that have been muted.

The table's columns are:

  • Provider: where the cluster runs (for example azure, gcp, or k8s for self-managed).

  • Usage Account: the account, subscription or project the cluster belongs to.

  • Resource ID: the workload, node or volume the recommendation applies to.

  • Resource Type: for example Deployment, daemonset or PersistentVolumeClaim.

  • Savings Type: Orphan, Idle or Rightsize.

  • Policy: the recommendation policy that produced it.

  • Severity: how much attention the recommendation deserves.

  • Cost: what the resource costs per month today.

  • Potential Savings: the estimated monthly saving if you make the change.

  • Action: the exact change to make, for example Lower the CPU request on container prometheus-collector of Deployment ama-metrics in namespace kube-system from 0.150 to 0.040 cores.

  • Reason: the evidence behind it, for example the current request against the 95th-percentile usage over the lookback period.

  • vTags and Tags: Virtual Tags and native tags on the resource.

Above the table, Select options lets you filter by Savings Type, Policy, Resource Type, Severity, Cluster or Namespace. You can also search, and download the table as CSV.

Recommendation Policies

Every recommendation comes from a policy that checks your clusters against a rule, using a lookback period of usage history. Policies are grouped by Savings Type:

  • Orphan: resources that nothing uses or is attached to.

  • Idle: workloads, nodes or devices that are running but doing no useful work.

  • Right Size: requests or sizes that are larger than measured use needs.

To learn about the policies: click the Settings icon in the page header to open Savings Settings, pick a tab (Orphan, Idle or Right Size), and click the info (i) icon next to a policy to see what it checks. The list of policies can change as new ones are added, so Savings Settings always shows the current set.

Savings Settings

Click the Settings (wrench) icon in the page header to open Savings Settings. It has three tabs (Orphan, Idle and Right Size), each listing its policies.

  • Use the toggle next to a policy to turn it on or off. A policy that is off stops producing recommendations.

  • Click the info (i) icon next to a policy to see what it does.

  • Expand a policy to set its Severity and Lookback Period (for example, Container CPU Request Rightsize shows Medium severity and a 30-day lookback).

  • Click Save to apply your changes, or Cancel to discard them.

It may take up to 24 hours for policy changes to take effect.

Actions and Filters

Header Icons

The page header has these icons:

  • Share: copies a link to the current page and its filters so you can send it to teammates.

  • Bookmark and Subscription: save this view, or have it emailed on a schedule. See Bookmarks and Subscriptions.

  • Screenshot: downloads the current page as a PDF.

  • Filters: filter the whole page by Provider, account, cluster and similar fields.

  • Settings: opens Savings Settings (above).

  • Reload: clears all filters and selections and returns the page to its default view.

  • Help: opens this page.

Troubleshooting

  • If a recommendation you expected isn't listed, check Savings Settings (the policy that produces it may be switched off, or its lookback period may be too short to see the pattern).

  • If you changed a policy and nothing moved, wait: policy changes can take up to 24 hours to take effect.

  • If the page is empty for a cluster, confirm the cluster is connected and reporting usage (see Kubernetes onboarding): recommendations need usage history to compare against requests.

FAQs

Where can I see what each policy does?
Click the Settings icon in the page header, choose the Orphan, Idle or Right Size tab, and click the info (i) icon next to the policy.

Is Potential Savings an amount I will see drop on an invoice?
Not directly. It is the value of reserved capacity you would hand back. On clusters you own, a cash saving appears only when freed capacity lets you retire or avoid nodes.

Why do I see only some Savings Types?
The Orphan, Idle and Rightsize widgets only show savings when a policy of that type finds something. A $0.00 widget means nothing was flagged for that type, not that the page is broken.

How do I stop a recommendation I don't plan to act on?
Mute it so it moves to the muted view, or turn off the policy that produced it in Savings Settings if you never want that kind of recommendation.