Replies: 1 comment 2 replies
-
Calico by default picks the interface randomly. If you added a new interface and restarted the node, it could have chosen the new interface. When you have multiple NICs, you should use one of the Calico methods to set the interface: https://docs.tigera.io/calico/latest/reference/installation/api#operator.tigera.io/v1.NodeAddressAutodetection |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am trying to build a cluster with 3 control planes and 4 agents. I am using Calico as the CNI. Everything was working great until I added a new network interface to the agents.
After adding a new network interface, I noticed that DNS resolution stopped working. On closer inspection, I found that the communication over VXLAN between the nodes is faulty. In tcpdump, I can see that the response on the control plane running the core DNS agent is going back through the newly added network interface instead of the correct one. I've tried to force the traffic flow with options like bind-address, node-ip & advertise-address, but the behavior remains the same.
NIC's on an agent
default routing table on an agent
all routing tables on an agent
Beta Was this translation helpful? Give feedback.
All reactions