To troubleshoot calico network issues within guest clusters, debug logging is indispensable. In this post, lets look at the steps that are required to enable debug logging for Calico. We need to first scale down the tkg-controller-manager on the supervisor cluster as we do not want changes we make to the calico pods to be reset. STEP 1: Scale down the tkg-controller-manager From the vCenter Server, login to the control plane VM....
There are two CNIs that are avaiable for container networking in Tanzu kubernetes guest clusters: Antrea and Calico In this post, lets take a closer look at Calico and how to deploy and use Calicoctl Pods can fail if they do not get an ip address from the CNI. A common error is: k get events 4m31s Warning FailedCreatePodSandBox pod/validationservice-59cbc867c-pt7k5 (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "2c0a340dfe947ad27564e0b73d5efac7f13951a77aa9c0a6e5e5d90b7d299e4c": rate: Wait(n=1) would exceed context deadline 4m31s Warning FailedCreatePodSandBox pod/validationservice-59cbc867c-qhdjr (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "c0f9ecf1f5a73954bbc3733ff1342fec6896d339bc6039473765e5f143b7850d": rate: Wait(n=1) would exceed context deadline To view the ip blocks provided by IPAM(Calico) in the Tanzu Kubernetes cluster...