0

Recently added a kubenode to the existing kubeadm cluster using 

kubeadm join --token (TOKEN) (MASTER IP):6443

and with 

--discovery-token-ca-cert-hash.

The node attached successfully and it is listed in the "kubectl get nodes".

Now the pods are assigned to the node, but those pods are restarted automatically and it seems this pods cannot communicate the other node pods also.

ADyson
  • 57,178
  • 14
  • 51
  • 63
Vijayan Jayabal
  • 1
  • Can you add more details here? What do you see in pod logs? How many times did the pods get restarted? – vjdhama Nov 30 '17 at 19:56
  • Consider including the output of 'kubectl get pods' and any other indication you might have that things aren't they way you want them to be. – Erik Nov 30 '17 at 19:57
  • look at the system logs in /var/log direcotry. – sfgroups Nov 30 '17 at 20:43
  • The token has expired so i have create the token using command kubectl generate token and use that token to join the node in to cluster. The node is showing into the cluster. but the pods running in the cluster is not working and keep restarted – Vijayan Jayabal Dec 01 '17 at 08:07

0 Answers0