CentOS Question posted in
The official documentation can be found here.

Cant access pod of another Node – CentOS

I install a 3 node Kubernetes Cluster with RKE tool. The installation was successful with no errors but I’m unable to ping from one pod to another pod.

If I ping a pod running on worker2 node(NODE-IP-10.222.22.47) I get a response, but no responses from pods running on worker1(NODE-IP-10.222.22.46).
enter image description here

My Pods are as follows –
enter image description here

Also I noticed for some pods it has given node-ip addresses. The node IP addresses are
Master1=10.222.22.45

Worker1=10.222.22.46

Worker2=10.222.22.47
cluster_cidr: 10.42.0.0/16

service_cluster_ip_range: 10.43.0.0/16

cluster_dns_server: 10.43.0.10

Overlay network – canal

OS- CentOS Linux release 7.8.2003

Kubernetes – v1.20.8 installed with rke tool

Docker – 20.10.7

Sysctl entries in all nodes

firewall was disabled in all nodes before install.

Check – sysctl net.bridge.bridge-nf-call-ip6tables

net.bridge.bridge-nf-call-ip6tables = 1

Check – sysctl net.bridge.bridge-nf-call-iptables

net.bridge.bridge-nf-call-iptables = 1

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    The reason was the UDP ports were blocked


  2. 0

    • From description and screenshots provided, some addons and
      controllers of master01 do not seem ready, which might need to be
      reconfigured.

    • You can also use routes to connect to pods on worker1. Check this for
      detailed instructions.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search