New server is added to the cluster and able to see this new node when I run "kubectl get nodes"
But noticed that kube-proxy is not running on this new node and due to that, on deploying the pod to this node, it is unable to communicate with other pods/containers running on other worker nodes.
I do see this error in kubelet logs continuously. But "systemctl status docker" shows that docker is running.
E0215 15:12:57.491851 1338 container_manager_linux.go:625] error opening pid file /run/docker/libcontainerd/docker-containerd.pid: open /run/docker/libcontainerd/docker-containerd.pid: no such file or directory
Any ideas, why kube-proxy pod is not running on this new worker node?
joshuatonga
commented
6 years ago
Hi,
I have setup kubernetes on coreOS by following this doc and everything is working OK.
https://coreos.com/kubernetes/docs/latest/getting-started.html
After few days, I am trying to add new worker node to the existing cluster as per this doc https://coreos.com/kubernetes/docs/latest/deploy-workers.html
New server is added to the cluster and able to see this new node when I run "kubectl get nodes"
But noticed that kube-proxy is not running on this new node and due to that, on deploying the pod to this node, it is unable to communicate with other pods/containers running on other worker nodes.
I do see this error in kubelet logs continuously. But "systemctl status docker" shows that docker is running.
E0215 15:12:57.491851 1338 container_manager_linux.go:625] error opening pid file /run/docker/libcontainerd/docker-containerd.pid: open /run/docker/libcontainerd/docker-containerd.pid: no such file or directory
Any ideas, why kube-proxy pod is not running on this new worker node?