reason

Due to different installation methods, my calico failed to start when I installed it. It is estimated that the download of the image failed here. Learning from Baidu’s post, I personally agree with it. It probably means that although the domestic image address has been initialized and modified, the official foreign image will also be pulled when I installed calico

My installation method is: kubectl apply – F https://docs.projectcalico.org/v3.18/manifests/calico.yaml

Error form:

when viewing pod, calico cannot start normally. When using describe to view calico node, the image displayed fails, as shown in the following figure

solve

Using WGet https://docs.projectcalico.org/manifests/calico.yaml Command Download calico.yaml Form a local file

execute kubectl delet – F calico.yaml Delete calico that failed to download before

Then execute kubectl apply – F calico.yaml That is

summary

I don’t know why this is so. It’s easy to report an error when downloading and installing directly. Only when the download is completed locally can the installation be successful. Friends with the same problems can try this method