TKG cluster nodes created without EXTERNAL-IP

Products

• VMware Tanzu Kubernetes Grid Management
• Tanzu Kubernetes Grid
• VMware Tanzu Kubernetes Grid
• VMware Tanzu Kubernetes Grid 1.x
• VMware Tanzu Kubernetes Grid Plus
• VMware Tanzu Kubernetes Grid Plus 1.x

Issue/Introduction

During an upgrade or recreation of a cluster node, the EXTERNAL-IP is not set for the new node.

Cause

The node has not been initialised with the cloud provider (vCenter)

Resolution

Check connectivity from new node to vCenter FQDN

curl -v https://<vCenter FQDN>

 

Check the vCentre thumbprint is valid. Review the CPI logs and the vCenter thumbprint.

kubectl logs -n kube-system <vsphere-cloud-controller-manager pod>

echo |openssl s_client -connect <vCenter FQDN>:443 2>/dev/null | openssl x509 -noout -fingerprint -sha1

 

Refer to KB to change vCenter thumbprint on TKG