-
Notifications
You must be signed in to change notification settings - Fork 560
FailedNodeAllocatableEnforcement on cgroups-per-qos false #2263
Comments
+1 |
I am getting the same issue on an K8s 1.9.2 cluster using acs-engine 0.12.5 engine. In fact over 19K time over 3 days. @yastij @karataliu @feiskyer |
@jcharlytown We are observing the same issue. According to the docs the |
cc @arnaudmz |
PR #2310 aims to fix this |
Thanks everyone for fixing this. +1! |
I just checked the latest release - it seems this fix is not included. Is there any specific reason? |
cc @jackfrancis |
@jcharlytown @yastij Are you able to build from master to deploy clusters? If there is an overwhelming desire for a patch release we can include this fix in such a release this week. |
@jackfrancis, I can build from master, yes. I was just wondering why that was in general. To understand the procedures here might come in handy in the future as we are currently evaluating what tool chain to use to manage our clusters. Can you comment on why this was not included? |
@jackfrancis - would be really nice, thanks ! |
We generate a patch release when there is a wide-impacting fix that we want to encourage folks to opt into. This is why it's important to vote when you want to see something sooner than the next minor release. So if there's a v0.13.2, we'll include this in it. :) Additionally in the future we plan to patch release when a new Kubernetes release is published to make it easier to deploy new clusters (without requiring users to build from master). |
SGTM |
Is this a request for help?:
Yes
Is this an ISSUE or FEATURE REQUEST? (choose one):
Issue
What version of acs-engine?:
As of now all shipping with PR #1960
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Tested with Kubernetes 1.8.4, 1.8.6, 1.8.7
What happened:
Kubelets constantly file events like this:
What you expected to happen:
This warning not to pop up, i.e.,
Normal NodeAllocatableEnforced 4s kubelet, k8s-master-56038831-0 Updated Node Allocatable limit across pods
insteadHow to reproduce it (as minimally and precisely as possible):
Deploying cluster using this model (I removed some secrets and ssh key):
Afterwards running
kubectl describe node <NODE>
on the new cluster - the described event should pop up.Manually changing
/etc/default/kubelet
and changing--cgroups-per-qos
totrue
instead offalse
makes the event disappear. However, I have not further investigated whether or not this has other side effects.Hence, I have two questions: a) Am I the only person experiencing this? And, b) what is the rational behind changing this argument from
true
(as per default) tofalse
and making it static at the same time?Also, am I missing something? As far as I can tell I am not doing anything specific, this should be a very plain setup?
Anything else we need to know:
The text was updated successfully, but these errors were encountered: