Welcome to the Linux Foundation Forum!

calico controller CrashLoopBackOff


I am getting error while configuring calico controller vi kubesphere kubekey tool, below is the error

"2023-07-29 20:41:33.458 [INFO][1] main.go 98: Loaded configuration from environment config=&config.Config{LogLevel:"info", WorkloadEndpointWorkers:1, ProfileWorkers:1, PolicyWorkers:1, NodeWorkers:1, Kubeconfig:"", DatastoreType:"kubernetes"}
W0729 20:41:33.459145 1 client_config.go:617] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
2023-07-29 20:41:33.460 [INFO][1] main.go 119: Ensuring Calico datastore is initialized
2023-07-29 20:41:43.460 [ERROR][1] client.go 272: Error getting cluster information config ClusterInformation="default" error=Get "": context deadline exceeded
2023-07-29 20:41:43.460 [FATAL][1] main.go 124: Failed to initialize Calico datastore error=Get "": context deadline exceeded"

all pods including calico nodes are running fine

Thanks & Regards


  • chrispokorni
    chrispokorni Posts: 2,163

    Hi @syedhamzaakhter,

    The course material and the lab guide are focusing on the upstream Kubernetes project, with kubeadm as the cluster bootstrapping tool, and calico as the pod network plugin chosen for the lab cluster.

    The Kubernetes distribution installed above may already come pre-installed with a pod network plugin. In general, for these pod network plugins to function as intended, certain firewall rules may need to be put in place to allow necessary protocols to reach specific port numbers. Calico may be different than your existing pod network plugin, and it may need additional or different firewall rules.

    I would recommend inspecting the official documentation of your bootstrapping tool to learn how to successfully install and configure other pod network plugins for you Kubernetes distribution.



Upcoming Training