-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kube/System Reserved resources should be enabled by default #318
Comments
I am guessing in the vast majority of cases users would prefer nodes not to go offline when they become oversubscribed, so let's have that as the default please 😄 |
Something that just bit us too (my fault ultimately for not setting better resource limits) but would be great to be safe by default! @max-rocket-internet does GKE set anything for system-reserved by default? |
@stefansedich |
@jnatten I took that was for kube-reserved, do they assign the same for both or split it up somehow? |
If you are having OOM errors, EKS support suggestion is:
and "adjust to your needs". So while we wait for this, we are using the GKE doc as reference |
Resolved in #350 |
Related,
|
What would you like to be added:
I think a small amount of CPU and memory should be reserved for kubelet by default: https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#kube-reserved
Why is this needed:
For stability.
I was recently running a load test and had some nodes go
NotReady
with error:Kubelet stopped posting node status
. I know it's possible to add kubelet args manually but I think this should be the default.I lot of people with related problems in #79
For reference, a GKE node with 2 CPUs and 7.5GB of memory has this in
/home/kubernetes/kubelet-config.yaml
:Like many aspects of EKS, it would be great if we just copied GKE 😅
The text was updated successfully, but these errors were encountered: