Welcome to the Linux Foundation Forum!

Lab 3.2: Grow the Cluster

anindya2
anindya2 Posts: 3
in LFS258 Class Forum

Hi, I am trying to join the 2nd node to the cluster but after almost 10 min past nothing showing , I am using EC-2 ubunto image i.e ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20200129 (ami-08bc77a2c7eb2b1da) and 2CPU , 8GB RAM for both the VMs .. I am stuck at below ,can anyone please let me know what could be the issue ?

root@ip-172-31-90-237:~# kubeadm join --token gx404l.isfrgeagyslohdsr k8smaster:6443 --discovery-token-ca-cert-hash sha256:7a74fb765dccf0f5aeeabb58d03e2ecc696b0475f87a9b39fbbf2bfbcfc625c9
[preflight] Running pre-flight checks
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/

Thanks !
Anindya

Comments

  • anindya2
    anindya2 Posts: 3

    ubuntu@ip-172-31-83-128:~$ sudo bash
    root@ip-172-31-83-128:~# kubectl get nodes
    NAME STATUS ROLES AGE VERSION
    ip-172-31-83-128 Ready master 32m v1.16.1
    root@ip-172-31-83-128:~#
    root@ip-172-31-83-128:~#
    root@ip-172-31-83-128:~# exit
    exit
    ubuntu@ip-172-31-83-128:~$
    ubuntu@ip-172-31-83-128:~$
    ubuntu@ip-172-31-83-128:~$ kubectl get nodes
    NAME STATUS ROLES AGE VERSION
    ip-172-31-83-128 Ready master 32m v1.16.1
    ubuntu@ip-172-31-83-128:~$

  • chrispokorni
    chrispokorni Posts: 2,592

    Hi @anindya2,

    Similar issues have been reported earlier in the forum. They were caused by either restrictive Security Groups and/or by misconfigured /etc/hosts file on the worker/second node.

    The SG rules need to allow all ingress traffic from all sources, to all ports and all protocols.

    Regards,
    -Chris

  • anindya2
    anindya2 Posts: 3

    Thank you Chris , I has issue with the ingress traffic.

Categories

Upcoming Training