This message was deleted.

I would look at the pod events using kubectl describe to start and see what is failing. So for example:

kubectl describe pod -n kube-system $pod_name

whenever a new container is being created, i see events such as below, Warning FailedCreatePodSandBox <invalid> kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "3cb977300764122ad65fcb76fcdce71715254401eea23409e0a768b628d3cf24": plugin type="calico" failed (add): error getting ClusterInformation: Get "https://10.43.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": Service Unavailable Normal SandboxChanged <invalid> (x3 over <invalid>) kubelet Pod sandbox changed, it will be killed and re-created.