I'm trying to create a Kubernetes cluster on AWS. I've installed all the dependencies and done the kubeadm init. kubeadm init --apiserver-advertise-address= --pod-network-cidr=192.168.0.0/16 I even got the command to join the node to the cluster. I have two problems: 1. I get nodes in the notReady status when i do kubectl get nodes 1 why is that so? 2. Two of my codedns pods are stuck in containercreating state 2 Why is this happening?
Asked
Active
Viewed 9,310 times
1
-
1SUrely the containerCreating status is because there is no ready nodes. You should get kubelet logs from the nodes to see what's happening. – Ignacio Millán Oct 10 '18 at 09:58
-
when I do kubectl describe pod
, I get an error saying pod not found. – Kalgi Shah Oct 10 '18 at 10:13 -
Is it because you are using unlicensed Windows :) as shown in the screen captures. Just kidding. – Praveen Sripati Oct 10 '18 at 11:19
-
Hahah I wish that was the issue, could have been sorted easilt :p – Kalgi Shah Oct 10 '18 at 13:54
1 Answers
2
According to the screenshots attached, I assume that you didn't deploy any CNI network into your cluster; as a result, coredns Pods are in failed status.
I recommend installing one of the Pod network addons from the link above. In case of any re-occurred issue, try to bootstrap cluster from scratch. You can find a good article here with detailed instruction for kubeadm installation procedure published by @VKR.
In case of any errors during the installation, post them below this answer.
Nick_Kh
- 5,089
- 2
- 10
- 16
-
-
Great! If you found that solution fixed you issue, kindly accept the answer, so the other contributors will know a way solving the similar problem. – Nick_Kh Oct 11 '18 at 09:01
-
I have a related question.. Are you willing to comment? Here is the link: https://stackoverflow.com/questions/55112356/are-these-pods-inside-the-overlay-network – CodeMed Mar 12 '19 at 00:32