Kubernetes Resource Quantity Calculator

Convert seamlessly between CPU cores/millicores and memory units (Mi, Gi, MB, GB) to build accurate Kubernetes pod resource limits and requests snippets.

CPU Allocation

CPU Value:

In Millicores: 500m

In Full Cores: 0.5

Memory Allocation

Memory Value:

Binary (MiB / GiB): 512Mi

Decimal (MB / GB): 536.8 MB

Spec Block Options:

Include resources.requests block

Include resources.limits block

Generated Container Resources Snippet: Ready

Resource Quantity Guidelines

1. CPU Units Explanation

1 CPU core equates to 1000m (millicores). Kubernetes CPU limits dictate guaranteed share slices of physical hyperthreads.

2. Memory Units Convention

Always prefer binary suffixes like Mi and Gi (powers of 1024) to avoid runtime OOM discrepancies versus decimal MB/GB equivalents.

Frequently Asked Questions (FAQ)

Requests are utilized by the scheduler to place pods onto nodes with sufficient capacity. Limits cap maximum resource consumption to prevent runaway workloads.

If a container goes over its specified memory limit, the Linux kernel terminates the process, resulting in an OOMKilled pod status exit code 137.

Yes, expressions like 0.1 or 1.5 cores are fully valid Kubernetes resource quantity inputs, though many engineers prefer millicores (e.g., 100m or 1500m).