Closed
Description
Why do you want this feature?
In EKS, nodes that starve for resources for system daemons go to NotReady state and stay there until someone manually deletes the node in EC2 UI. The feature of a timeout from the master to a node if it stays NotReady for too long because it can't comunicate will come with kubernetes 1.15 (in 2020). Reserving resources is very important https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/
What feature/behavior/change do you want?
There should be a field in the cluster config yaml to configure this settings and that applies them to the userdata in the cloudformation template, something like extraKubeletFlags
or appendToKubeletConfig
it would look like:
appendToKubeletConfig:
kubeReserved:
cpu: "300m"
memory: "300Mi"
ephemeral-storage: "1Gi"
kubeReservedCgroup: "/kube-reserved"
systemReserved:
cpu: "300m"
memory: "300Mi"
ephemeral-storage: "1Gi"
evictionHard:
memory.available: "200Mi"
nodefs.available: "5%"