Hello! I have a Rancher 2.8.1 HA running on an EKS...
# azure
c
Hello! I have a Rancher 2.8.1 HA running on an EKS 1.25 cluster via Transit Gateway & DirectConnect. I've built out a private-only AKS 1.27 cluster with non-routable CIDR blocks configured for the Service CIDR, DNS IP and Pod CIDRs. The nodes spin up with routable IPs and we connect via ExpressRoute to the Sub/RG. I try and do a generic cluster import with Rancher and the agent yaml deploys fine. It connects back to the Rancher cluster but it fails reaching back out the agent pod because it's non-routable and I don't have any NAT gateways or anything enabled. Rancher is not in the same VNet or Subnet so my plan is to deploy nginx to the cluster and set up a Load Balancer and ingress service to access the rancher agent pod. Is this typically how folks resolve this type of issue? Just curious as to what others have done.