Kubernetes priority classes can preempt security controls
Kubernetes priority controls scheduling order, not trust. A PriorityClass maps a name to an integer, and a pod with a higher value may cause lower-priority pods to be evicted when the cluster needs capacity. The feature is useful for latency-sensitive services and critical jobs. It can also remove the pod that performs logging, policy enforcement, or incident response.
The Kubernetes documentation warns that users who can create high-priority pods can disrupt other workloads in a cluster where not all users are trusted. That warning applies beyond ordinary applications. An admission controller, security agent, or monitoring collector with a modest priority can be displaced by a workload with a higher one. A PodDisruptionBudget does not make the control absolute.…