Why is cilium given 30% of a nodes CPU on a Kubernets cluster?
I noticed that the cilium pods are generously provisioned on a DO k8s cluster. It seems a little excessive provision 30% of the CPU with no upper limit. Given it’s a Go project, and they’re usually quite performant, this reasonable?
kube-system cilium-crswr 300m (30%) 0 (0%) 0 (0%) 0 (0%) 10d
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×