Calico-node in the Running State But Not Ready
Symptom
After Calico is deployed on Kubernetes, the Calico-node is in the Running state instead of the Ready state.
Key Process and Cause Analysis
As shown in the following figures, Docker logs show that the dataplane updates operation is being performed and the resync connection cannot be set up. The calicoctl tool is used to query node information on the primary node. It is found that some nodes have dual network planes. However, the calico component uses AUTO_DETECTION to discover BGP network interfaces by default. The external network interfaces are incorrectly selected on these nodes. As a result, the nodes cannot communicate with each other.
Conclusion and Solution
You are advised to use nodeSelector + IP_AUTODETECTION_METHOD to distinguish these nodes and manually identify BGP network interfaces.
Parent topic: Troubleshooting