A PDF rendering Pod writes large temporary files under the container filesystem and occasionally fills the node. Which resource setting specifically governs that scratch usage?
Select an answer to reveal the explanation.
Short Explanation
Scratch PDFs pile up like junk on a shared desk—ephemeral-storage is the quota for that desk space. Put requests and limits on ephemeral-storage so the platform can schedule and evict fairly. CPU bumps and readiness probes don't meter local disk fill.
Full Explanation
Containers that write heavily to the writable layer or emptyDir consume node ephemeral storage. Declaring resources.requests and resources.limits for ephemeral-storage lets the scheduler account for scratch needs and enables eviction when limits are exceeded. Raising CPU alone, mounting host root, or using readiness probes does not replace ephemeral-storage resource controls.