New See exactly what you're overpaying AWS in under 60 seconds. Try the Calculator for free →

Kubernetes Resource Requests

A Kubernetes resource request is the minimum amount of CPU or memory a container declares it needs, which the scheduler uses to decide which node to place it on.

How It Works

When you deploy a container in Kubernetes, you can specify two resource settings: a request and a limit. The request tells the scheduler the baseline resources the container expects to use. The scheduler uses this value to find a node with enough available capacity to host the pod. If no node can satisfy the request, the pod stays unscheduled until capacity opens up. The request does not cap what the container can consume; that is what limits are for. On AWS this runs through Amazon EKS, on Azure through AKS (Azure Kubernetes Service), and on GCP through GKE (Google Kubernetes Engine).

Why It Matters for Cloud Cost

Misconfigured resource requests are one of the most common sources of waste in container-based environments. Setting requests too high causes nodes to appear full before their actual compute is exhausted, forcing premature node scale-outs and inflating your EC2, VM, or Compute Engine bill. Setting requests too low causes the scheduler to overpack nodes, which leads to CPU throttling, out-of-memory kills, and degraded application performance. Neither extreme is free. Teams that do not audit resource requests regularly end up paying for node capacity that never gets used, or absorbing the operational cost of instability caused by undersized pods.

Usage AI includes ClearCost, a showback and visibility layer that gives FinOps teams cost reporting across cloud accounts, supporting the broader effort to identify and reduce waste from overprovisioned workloads.

See how Usage AI saves 30 to 50% on AWS, GCP, and Azure.