Configure QoS to guaranteed for Weave-net gets ignored.

[dennisTGC]

What you expected to happen?

After settings limits as specified in the k8s docs and the weave readme we don't see the QosClass change to guaranteed.

Also, in other documentation the question is if this is neccessary as the priorityClassName: system-node-critical is already used and merged as seen in #3691

So I don't understand fully:

• is setting the priorityClassName enough?
• if setting the ds is of added value, why does the qosClass doesn't change to guaranteed?

What happened?

after setting limits in the daemonset of weave, the qosClass: Burstable remained and did not change to guaranteed. A daemonset restart did also not help.

How to reproduce it?

Add limits with the same specs as the requests for each container.

Anything else we need to know?

• running on own hardware
• used kubeadm for k8s deployment

Versions:

weave script 2.8.1
docker:18.06.3-ce
uname: 5.4.0-91-generic #102~18.04.1-Ubuntu
k8s: 1.16.15