calico: don't set calico-node cpu limits by default (#11914)
Upstream calico isn't doing that, and: - this can cause throttling - the cpu needed by calico is very cluster / workload dependent - missing cpu limits will not starve other pods (unlike missing memory requests), because the kernel scheduler will still gives priority to other process in pods not exceeding their requests
Loading
Please register or sign in to comment