Two coredns Pods in k8s cluster are in pending state

9/24/2019
kube-system   coredns-f68dcb75-f6smn           0/1     Pending   0          34m
kube-system   coredns-f68dcb75-npc48           0/1     Pending   0          34m
kube-system   etcd-master                      1/1     Running   0          33m
kube-system   kube-apiserver-master            1/1     Running   0          34m
kube-system   kube-controller-manager-master   1/1     Running   0          33m
kube-system   kube-flannel-ds-amd64-lngrx      1/1     Running   1          32m
kube-system   kube-flannel-ds-amd64-qz2gn      1/1     Running   0          32m
kube-system   kube-flannel-ds-amd64-w5lpc      1/1     Running   0          34m
kube-system   kube-proxy-9l9nv                 1/1     Running   0          32m
kube-system   kube-proxy-hvd5g                 1/1     Running   0          32m
kube-system   kube-proxy-vdgth                 1/1     Running   0          34m
kube-system   kube-scheduler-master            1/1     Running   0          33m

I am using the latest k8s version: 1.16.0.

kubeadm init --pod-network-cidr=10.244.0.0/16 --image-repository=<some-repo> --token=TOKEN --apiserver-advertise-address=<IP> --kubernetes-version=1.16.0

This is the command I am using to initialize the cluster

The current state of the cluster.

master   NotReady   master   42m   v1.16.0
slave1   NotReady   <none>   39m   v1.16.0
slave2   NotReady   <none>   39m   v1.16.0

Please comment if you need any other info.

-- SidhuMooseWala
docker
kubernetes

1 Answer

9/24/2019

I think you need to wait for k8s v1.17.0 or update your current installaion, this issue fixed in here

orginal Issue

-- LinPy
Source: StackOverflow