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?
0
votes
SUrely 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
when I do kubectl describe pod <pod_name>, I get an error saying pod not found.
– Kalgi Shah
Is it because you are using unlicensed Windows :) as shown in the screen captures. Just kidding.
– Praveen Sripati
Hahah I wish that was the issue, could have been sorted easilt :p
– Kalgi Shah
1 Answers
1
votes
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.
