311 ticket workers on OKE must land on nodes with enough free capac…

Question

311 ticket workers on OKE must land on nodes with enough free capacity, yet noisy neighbors must not consume unbounded CPU. How should the Pod spec express that?

Accepted Answer

Set CPU and memory requests for scheduling placement and limits to cap what each container may consume — Requests are the reservation card that gets the Pod a seat; limits are the "no second helpings" cap. Zero requests with huge limits invites noisy neighbors. On managed or virtual nodes, put CPU and memory in the Pod spec so placement and caps are explicit.

Answer

Set only huge limits with zero requests so the scheduler ignores capacity and every Pod packs onto one node

Answer

Omit requests and limits so virtual nodes invent shapes from the Deployment name

Answer

Put resource numbers only in a ConfigMap; the kube-scheduler never reads the Pod spec for capacity

311 ticket workers on OKE must land on nodes with enough free capacity, yet noisy neighbors must not consume unbounded CPU. How should the Pod spec express that?

Short Explanation

Full Explanation