Worker Node Intermittently Entering Into "Ready, SchedulingDisabled" State
PreviousThe Command pf9ctl cluster prep-node Fails to Onboard The Host Due To Unavailability of The NTP PackNextPod 'calico-typha' Not Running on Master Node
Last updated
One or more Kubernetes nodes are intermittently transitioning into a "Ready, SchedulingDisabled" state, where Kubelet is still heartbeating, but, workloads are no longer able to be scheduled to the node.
Platform9 Managed Kubernetes - All Versions
Kubelet
The node(s) which are impacted are likely facing resource contention/exhaustion - CPU and/or Memory – which prompts scheduling to be disabled for the node by kube-controller-manager, based on the node metrics reported by Kubelet.
Ensure that appropriate pod limits are set.
Ensure that the pod limits set are not excessive, i.e. set too low, which would cause continual pod restarts/evictions, and drive up the resource usage of the node all the same.
Last updated
