Verify connectivity to the registry
kubectl get pods -n tkr-system -o wide
kubectl get nodes -o wide
ssh capv@NODE-IP
curl -kv https://REGISTRY-FQDN:443Verify that you can download images from the registry
crictl pull REGISTRY-FQDN/IMAGE-PATHIf the above verification steps are successful, check for the known issue described in https://kb.vmware.com/s/article/86496.
Apply the workaround in this KB to the Worker VM and restart the tkr-controller-manager pod.
To apply the workaround at cluster creation time, copy the contents below in a file and save in ~/.tanzu/tkg/providers/infrastructure-vsphere/ytt.
See
documentation for further details on overlays as the directory is different for different TKG versions.
#@ load("@ytt:overlay", "overlay")
#@overlay/match by=overlay.subset({"kind":"KubeadmControlPlane"})
---
spec:
kubeadmConfigSpec:
preKubeadmCommands:
#@overlay/append
- ethtool -K eth0 tx-udp_tnl-segmentation off && ethtool -K eth0 tx-udp_tnl-csum-segmentation off && ethtool -K eth0 tx off && ethtool -K eth0 rx off
#@overlay/match by=overlay.subset({"kind": "KubeadmConfigTemplate"})
---
spec:
template:
spec:
preKubeadmCommands:
#@overlay/append
- ethtool -K eth0 tx-udp_tnl-segmentation off && ethtool -K eth0 tx-udp_tnl-csum-segmentation off && ethtool -K eth0 tx off && ethtool -K eth0 rx off