In Kubernetes, priorityClassName is an important scheduling control that determines the relative importance of pods. By assigning a PriorityClass, cluster operators can ensure that critical workloads are scheduled before lower-priority ones and are less likely to be evicted under resource pressure.
In multi-tenant or shared Kubernetes clusters, resource contention is common. Without a priorityClassName, the pods may be scheduled with default priority, meaning they compete equally with less critical workloads. Allowing operators to assign a high priority ensures the pods are less likely to be preempted or evicted during node pressure events.
Supporting priorityClassName in the Helm chart improves reliability, aligns with Kubernetes best practices, and gives operators control over pod scheduling and eviction policies, all with minimal implementation overhead.