Skip to main content
All of the catalog
Scenario

Cost & Capacity: Right-Sizing Over-Provisioned Resources

Deploy go-api with deliberately over-provisioned CPU and memory requests, observe the inflated cost in OpenCost, then right-size the requests to a realistic baseline. Checks verify that requests were reduced to the target thresholds while go-api stays healthy under traffic. Teaches the observe-measure-reduce loop that keeps platform costs rational.

CostVerifiedk3dkind
Definition on GitHub

What you'll do

  • Observe go-api's inflated cost in OpenCost and relate it to over-provisioned CPU/memory requests
  • Right-size the CPU request from 2000m to ≤100m and memory request from 1Gi to ≤256Mi
  • Verify go-api stays healthy under steady traffic with the reduced requests
  • Understand that requests drive scheduling and billing, while limits cap usage

Stages

  1. 1inflate

    Over-provision go-api's CPU/memory requests 40×/32× (the 'before' state to observe in OpenCost)

    go-api-overprovisioned

Prerequisites

These are installed into the lab cluster for you — listed so you know what the scenario actually depends on.

cost/opencostmonitoring/metricsingressgo-api

The incident field notes

One real Kubernetes failure a week — the symptom, the commands that found it, and the fix. Written from actual lab runs, not from memory.

You'll get the Kubernetes Incident Response Field Guide, plus occasional emails about new scenarios, posts and paid offerings such as courses and workshops. Unsubscribe any time.