Kubernetes the hardway

• Our issue with running the etcd cluster as service still exists so we have executed etcd from command line

/usr/local/bin/etcd \
>   --name ip-172-31-51-202 \
>   --cert-file=/etc/etcd/kubernetes.pem \
>   --key-file=/etc/etcd/kubernetes-key.pem \
>   --peer-cert-file=/etc/etcd/kubernetes.pem \
>   --peer-key-file=/etc/etcd/kubernetes-key.pem \
d-ca-file=/etc/etcd/ca.p>   --trusted-ca-file=/etc/etcd/ca.pem \

  --pee>   --peer-trusted-ca-file=/etc/etcd/ca.pem \
>   --peer-client-cert-auth \
>   --client-cert-auth \
>   --initial-advertise-peer-urls https://172.31.51.202:2380 \
>   --listen-peer-urls https://172.31.51.202:2380 \
>   --listen-client-urls https://172.31.51.202:2379,https://127.0.0.1:2379 \
>   --advertise-client-urls https://172.31.51.202:2379 \
>   --initial-cluster-token etcd-cluster-0 \
>   --initial-cluster controller-0=https://10.240.0.10:2380,controller-1=https://10.240.0.11:2380,controller-2=https://10.240.0.12:2380 \
>   --initial-cluster-state new

* Lets continue with the k8s control plane Refer Here

• Lets bootstrap the worker nodes Refer Here
• Status:
  • kubectl get nodes is not responding with nodes