On Windows hosts, there is a chance that the containerd process won't get enough CPU cycles because of the default priority set for the Windows process.
Having an additional flag to containerd similar to what we did for kubelet might be helpful, so that end user can specify what priority can be set for containerd
Let me know if this is a reasonable approach. I can work on it.
What is the problem you're trying to solve
On Windows hosts, there is a chance that the containerd process won't get enough CPU cycles because of the default priority set for the Windows process.
xref: https://github.com/kubernetes/kubernetes/issues/95735#issuecomment-719083689
Describe the solution you'd like
Having an additional flag to containerd similar to what we did for kubelet might be helpful, so that end user can specify what priority can be set for containerd
Let me know if this is a reasonable approach. I can work on it.
Additional context xref: https://github.com/kubernetes/kubernetes/issues/95735
cc @marosset @jsturtevant @aravindhp