We have a 3 node vRA 8.16.0 cluster which we have failed over to a new site using SRM.
Since doing so, the K8s services on the nodes refuse to start and we can't work out why. I can't share any logs directly due to the security requirements of the customer but the basic behaviour is as follows:
Servers boot in to a loop, where they try and start etcd.service, kube-apiserver.service and kubelet.service. None of these services start and the host just loops around trying to bring them up.
There are a variety of 503, 500 and Node Not Found errors in the logs for the above services.
We can't use any of the deploy.sh commands, because K8s isn't 'up' enough to be of any use.
We have verified that we reconfigured the nodes with the new DNS server information relevant to the site they have moved to. The nodes themselves didn't get readdressed as the segment they are on carries the same subnet.
I know this post is a little vague, for which I apologise, but any assistance would be appreciated.
