kube-proxy being evicted due to inode resource

[justinsb]

We need to protect kube-proxy from eviction; during low inode situations it often is evicted.

[a-chernykh]

Just experienced the same problem and created kubernetes/kubernetes#51432. I am not sure how it is possible for kubelet to evict a critical pod.

[a-chernykh]

According to https://v1-6.docs.kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/ critical pod also requires [{"key":"CriticalAddonsOnly", "operator":"Exists"}] toleration. It looks like kops does not set this toleration for kube-proxy:

kops/nodeup/pkg/model/kubeproxy.go

Line 177 in 1eb9949

Tolerations: tolerateMasterTaints(),

[a-chernykh]

I think this is only relevant when rescheduler is deployed. I don't have it.

[dashpole]

Is the critical pod feature gate enabled for your setup? The kubelet should not evict pods that are static and critical when this feature gate is enabled on the kubelet.

[a-chernykh]

I just realized that it's not and that kops does not enable this feature gate by default. Thanks for the hint. I was pretty sure that it should have been enabled by default because so many components in kops have this critical pod annotation.