Calico Pod Not Started Resulting in Pod to Pod Communication Failure

Problem

Calico Pod Not Started on a Node Resulting in Pod to Pod Communication Failure.

# kubectl logs -f -n kube-system calico-node-rn9fg

2021-11-19 16:05:46.394 [INFO][8] startup/startup.go 299: Early log level set to info
2021-11-19 16:05:46.394 [INFO][8] startup/startup.go 315: Using NODENAME environment for node name
2021-11-19 16:05:46.394 [INFO][8] startup/startup.go 327: Determined node name: 10.2.50.48
2021-11-19 16:05:46.397 [INFO][8] startup/startup.go 359: Checking datastore connection
2021-11-19 16:06:16.397 [INFO][8] startup/startup.go 374: Hit error connecting to datastore - retry error=Get https://10.21.0.1:443/api/v1/nodes/foo: dial tcp 10.21.0.1:443: i/o timeout
2021-11-19 16:06:47.398 [INFO][8] startup/startup.go 374: Hit error connecting to datastore - retry error=Get https://10.21.0.1:443/api/v1/nodes/foo: dial tcp 10.21.0.1:443: i/o timeout```

Environment

  • Platform9 Managed Kubernetes - All Versions

Answer

  • Network Manager was enabled on the node. On stopping and disabling the service, and restarting the network.service, pod came up properly.

  • PMK does not support Network Manager.


© 2025 Platform9. All Rights Reserved

On This Page
Calico Pod Not Started Resulting in Pod to Pod Communication FailureProblemEnvironmentAnswer