Which Pod/Container specification element carries the CPU and memory requests and limits for a container?

Which Pod/Container specification element carries the CPU and memory requests and limits for a container?

• A. limits
• B. requests
• C. resources
• D. quotas

Answer: (C)

The container’s CPU and memory requirements are defined in the resources field of the Pod/Container spec. This resources element groups two parts: requests and limits. Each part can specify CPU and memory values. Requests indicate what the scheduler should guarantee for the container, while limits cap how much the container can use at runtime. Quotas refer to namespace-wide constraints and aren’t used for per-container resources, and limits or requests alone do not cover both aspects. A typical example is resources: requests: cpu: 250m, memory: 64Mi; limits: cpu: 500m, memory: 128Mi. So, the element that carries the CPU and memory requests and limits is the resources field.

The container’s CPU and memory requirements are defined in the resources field of the Pod/Container spec. This resources element groups two parts: requests and limits. Each part can specify CPU and memory values. Requests indicate what the scheduler should guarantee for the container, while limits cap how much the container can use at runtime. Quotas refer to namespace-wide constraints and aren’t used for per-container resources, and limits or requests alone do not cover both aspects. A typical example is resources: requests: cpu: 250m, memory: 64Mi; limits: cpu: 500m, memory: 128Mi. So, the element that carries the CPU and memory requests and limits is the resources field.