Lab 3.5 No connectivity between cp node and deployment(pod) in worker node.

dgsison

Hello everyone,

How are you all?
I am doing lab 3.5 and I was trying point 20. But I can't see the nginx page from the cp node. The nginx pod is located on the worker node. I am using docker as container engine.
From the worker node I can see the nginx page perfectly.
Do you know what could be the reason?

$ kubectl get pods --all-namespaces -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
default nginx-7848d4b86f-q5nm2 1/1 Running 0 18m 192.168.171.67 worker
kube-system calico-kube-controllers-6fd7b9848d-m4ngp 1/1 Running 1 (26h ago) 27h 192.168.242.69 cp
kube-system calico-node-4z72s 1/1 Running 1 (26h ago) 27h 10.128.0.4 cp
kube-system calico-node-fsxg5 1/1 Running 1 (26h ago) 26h 10.128.0.5 worker
kube-system coredns-78fcd69978-kxtxk 1/1 Running 1 (26h ago) 27h 192.168.242.70 cp
kube-system coredns-78fcd69978-pg87c 1/1 Running 1 (26h ago) 27h 192.168.242.68 cp
kube-system etcd-cp 1/1 Running 1 (26h ago) 27h 10.128.0.4 cp
kube-system kube-apiserver-cp 1/1 Running 1 (26h ago) 27h 10.128.0.4 cp
kube-system kube-controller-manager-cp 1/1 Running 1 (26h ago) 27h 10.128.0.4 cp
kube-system kube-proxy-67x4s 1/1 Running 1 (26h ago) 27h 10.128.0.4 cp
kube-system kube-proxy-8gxb7 1/1 Running 1 (26h ago) 26h 10.128.0.5 worker
kube-system kube-scheduler-cp 1/1 Running 1 (26h ago) 27h 10.128.0.4 cp

It seems that all pods are healthy.

Thank very much.
Kind regards.

dgsison

Hello.
Finally, I found the issue. As I suspected the problem was the GCE firewall rules.
Apologies for opening this thread.

Best regards and have a nice day.
Thanks.