Hi all! I am creating downstream a RKE cluster using the Terraform rancher2 provider with nodes having private IP addresses only, using virtual network peering to connect the Rancher management cluster and downstream RKE vnets. Without using a load balancer all nodes are registered successfully but when I want to create the cluster with an addon deployment job for external ingress load balancer, some worker nodes are stuck indefinitely in "Registering state". The provisioning log for the cluster completes successfully and all pods in all namespaces are running and jobs completed. I was able to access the stuck nodes and look at the rancher-agent logs:

INFO: Arguments: --no-register --only-write-certs --node-name system1 --server <https://rancher.sauron.mordor.net> --token REDACTED --ca-checksum 928a476fa0b0610ef46217292d51ac438f4ffa56ea3b155f240ee89ff4c1f31b

INFO: Environment: CATTLE_ADDRESS=10.100.0.4 CATTLE_AGENT_CONNECT=mordor CATTLE_INTERNAL_ADDRESS= CATTLE_NODE_NAME=system1 CATTLE_SERVER=<https://rancher.sauron.kangaroot.net> CATTLE_TOKEN=REDACTED CATTLE_WRITE_CERT_ONLY=true

INFO: Using resolv.conf: nameserver 127.0.0.53 options edns0 search <http://u52yollp52yetgbxgli0ra2ssb.ax.internal.cloudapp.net|u52yollp52yetgbxgli0ra2ssb.ax.internal.cloudapp.net>
WARN: Loopback address found in /etc/resolv.conf, please refer to the documentation how to configure your cluster to resolve DNS properly
ERROR: <https://rancher.sauron.mordor.net/ping> is not accessible (Failed to connect to <http://rancher.sauron.mordor.net|rancher.sauron.mordor.net> port 443: Connection timed out)

Any idea ? I would greatly appreciate help on this! I opened an issue with the code used and provisioning log for the cluster: https://github.com/rancher/terraform-provider-rancher2/issues/972```