We logged in the TCA UI and see workload clusters in a disconnected state
Environment
3.0
Cause
This indicates an expired, outdated kubeconfig file in the TCA and TCACP appliance
Resolution
SSH into each control plane node of the guest cluster and run the kubeadm certs check-expiration command to validate the Kubernetes certificates. kubeadm certs check-expiration
If the certificates are still valid, copy the kubeconfig context located at /etc/kubernetes/admin.conf from a single valid the control plane node.
cat /etc/Kubernetes/admin.conf
Next, go to the TCA Manager and update the cluster's kubeconfig in the Virtual Infrastructure section using the copied admin.conf file.
Access the TCA-CP dashboard on port 9443 and update the cluster’s kubeconfig there as well using the same file.
After both updates are complete, reboot the TCA Manager and TCA-CP appliances