Google cloud system kube-system namespaced deployed daemonsets not working
4/1/2020
We are having problem with several deployments in our cluster that do not seem to be working. But I am a bit apprehensive in touching these, since they are part of the kube-system namespace. I am also unsure as what the correct approach to getting them into an OK state is.
I currently have two daemonsets that have warnings with the message
DaemonSet has no nodes selected
See images below. Does anyone have any idea what the correct approach is?
-- The Kaizer
google-cloud-platform
kubernetes
Similar Questions
1 Answer
4/1/2020
A DaemonSet is creating a pod in each node of your Kubernetes cluster.
If the Kubernetes scheduler cannot schedule any pod, there are several possibilities:
- Pod spec has a too high memory requests resource for the memory node capacity, look at the value of
spec.containers[].resources.requests.memory - The nodes may have a taint, so DaemonSet declaration must have a toleration (kubernetes documentation about taint and toleration)
- The pod spec may have a
nodeSelectorfield (kubernetes documentation about node selector) - The pod spec may have an enforced node affinity or anti-affinity (kubernetes documentation about node affinity)
There are not the only solutions possible. More generally, a good start would be to look at the events associated to the daemon set:
> kubectl describe daemonsets NAME_OF_YOUR_DAEMON_SET-- Kartoch
Source: StackOverflow