Calico Network Plugin Is Not Ready
Symptom
After the kubectl get pod -A command is used to check the Calico network plugin, the value in the READY column is 0/1.
Possible Cause
If the network segment of a physical machine conflicts with that of the configured container or the physical machine is in a complex network environment, Calico cannot correctly identify valid NICs of the master and worker nodes.
Solution
Check whether the network segment of the physical machine is the same as that of the container. If yes, initialize the Kubernetes cluster again and change the value of pod-network-cidr to a network segment that does not conflict with the container network segment. After the initialization, change the value of Calico accordingly.
Start the default container network segment parameter CALICO_IPV4POOL_CIDR in the YAML file. You are advised to add the IP_AUTODETECTION_METHOD configuration. The value is can-reach={masterIP}, where masterIP indicates the IP address of the physical machine where the Kubernetes management node is located. The following figure shows the content that needs to be modified in the YAML file for starting Calico. For details about how to reset and install the Kubernetes, see the official Kubernetes website.
