Kubernetes Resource Request/Limit Calculator
Average and peak memory/CPU usage, turned into a resources.requests/limits YAML snippet - with the common OOMKill mistake explained.
resources:
requests:
memory: "180Mi"
cpu: "100m"
limits:
memory: "384Mi"
cpu: "480m"Requests come from average usage (what the scheduler reserves). Limits come from peak usage plus headroom (what triggers throttling or an OOMKill) - setting limits from average usage is the most common cause of surprise OOMKills under load.
Was this tool helpful?
See this same kind of analysis applied to your whole repository
Call graphs, dead code, blast radius, and a health score. Results in 60 seconds, free.
Related tools
See all Kubernetes tools →Kubernetes Probe Generator
Liveness, readiness, or startup - HTTP, TCP, or exec - a valid probe YAML block with correct successThreshold rules.
Kubernetes HPA Calculator
Current replicas and utilization to the exact replica count the HPA controller would scale to, plus a valid HPA YAML.
Kubernetes ConfigMap / Secret Generator
Key-value pairs to a valid ConfigMap or Secret manifest, Secret values base64-encoded correctly.
Kubernetes Ingress Generator
Host, path, backend service, and optional TLS - a valid networking.k8s.io/v1 Ingress manifest.
Kubernetes PodDisruptionBudget Calculator
Replica count and minAvailable/maxUnavailable to exactly how many pods can be evicted at once, plus a valid PDB manifest.
Runs entirely in your browser. Nothing is stored. Free forever.
