Feature request
Could you please add the possibility to define a (Kubernetes-native) priorityClassName in EventListeners?
Use case
When load on our Kubernetes cluster is high, Tekton EventListener pods get evicted because they have a default priority of 0, which is less than other workload on our cluster therefore the pod scheduler targets EventListener pods for eviction and kill them during high load.
If we would have the possibility to define a priorityClassName for EventListener pods, we would just use a priorityClassName with high priority value so that EventListener pods don't get evicted and always stay up.
Feature request
Could you please add the possibility to define a (Kubernetes-native) priorityClassName in EventListeners?
Use case
When load on our Kubernetes cluster is high, Tekton EventListener pods get evicted because they have a default priority of 0, which is less than other workload on our cluster therefore the pod scheduler targets EventListener pods for eviction and kill them during high load.
If we would have the possibility to define a priorityClassName for EventListener pods, we would just use a priorityClassName with high priority value so that EventListener pods don't get evicted and always stay up.