Civic payment Pods must receive Guaranteed QoS so they are last to be evicted under memory pressure. What resources configuration achieves that for every container?
Select an answer to reveal the explanation.
Short Explanation
Guaranteed is the matching-luggage rule: request and limit tags must say the same weight for CPU and memory on every container. PriorityClass can help scheduling preference, but it does not invent Guaranteed by itself.
Full Explanation
Guaranteed QoS requires that for every container, CPU and memory requests are set and equal to their respective limits. Leaving a resource unset or setting requests below limits yields Burstable (or BestEffort if nothing is set). PriorityClass affects priority and preemption behavior but does not replace the resources equality rule for Guaranteed classification.