fluentd: Support priorityClassName in DaemonSets
Closed this issue · 1 comments
TirTech commented
Currently neither of the fluentd DaemonSets support setting a priorityClassName.
We've experienced issues where nodes get filled by equally-high (default) priority pods first which leaves the fluentd pod pending when the node hits capacity. Since it's a DaemonSet, no scaling happens and the pod stays pending till space is made. With priorityClassNames we could ensure the fluentd pods get scheduled and not evicted unnecessarily.
I can make the PR for this if it's okay to do so.
Doron-Bargo commented
Hi @TirTech
Thanks for letting us know about this issue
If you want to contribute a PR we will be more than happy :)