Platform & DevOps·Placement, resources and the pod lifecycle
the workload with no requests set was the first one killed when the node ran out of memory, and nobody had chosen that.
Quality of service class
Also calledQoS class, guaranteed burstable besteffort
A classification the platform derives from your requests and limits, which decides the order things are killed under pressure: equal requests and limits are protected, requests below limits are burstable, neither set is expendable. It is not a field you set, it is a consequence of two fields you did set, which is why teams are surprised by their own ranking. Anything whose loss would be an incident should be in the protected class deliberately.