Hi CKAers, I have deployed a 3 (1 master and 2 worker) node cluster . I have use . . .

Kubernetes-Slack Discussions
#1

Satyam Sareen:
Hi CKAers,
I have deployed a 3 (1 master and 2 worker) node cluster .
I have used flannel as networking add-on and used the below command
kubectl apply -f <https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml>
But pods are not able to reach each other :
kube-system pods are in running state.
Any help will be greatly appreciated

ubuntu@master:~$ kubectl get po -n kube-system
NAME                             READY   STATUS    RESTARTS   AGE
coredns-78fcd69978-468vg         1/1     Running   0          23m
coredns-78fcd69978-9jcvh         1/1     Running   0          23m
etcd-master                      1/1     Running   0          23m
kube-apiserver-master            1/1     Running   0          23m
kube-controller-manager-master   1/1     Running   0          23m
kube-flannel-ds-csmbc            1/1     Running   0          13m
kube-flannel-ds-nfdlq            1/1     Running   0          13m
kube-flannel-ds-s2jpc            1/1     Running   0          13m
kube-proxy-99gqm                 1/1     Running   0          20m
kube-proxy-mbxw5                 1/1     Running   0          20m
kube-proxy-plmp2                 1/1     Running   0          23m
kube-scheduler-master            1/1     Running   0          23m
#2

unnivkn:
https://kodekloud.slack.com/archives/CDR9R5QRG/p1627418280382800

#3

unnivkn:
try this: its already there in the above link.

#4

unnivkn:
k run frontend --image=nginx --expose --port=80
k run backend --image=nginx --expose --port=80
k get po,svc

k exec frontend – curl backend
–wkg

k exec backend – curl frontend
–wkg

#5

Satyam Sareen:
Thankyou @unnivkn

#6

Satyam Sareen:
it was an issue with my security group, flannel uses different ports than weave

#7

Satyam Sareen:
so had create new sg rules

#8

unnivkn:
okie… so your k8s cluster is on cloud ?

#9

Satyam Sareen:
yup, ec2 machines on aws