05/13/2022, 6:28 PM
Hi all. I have created downstream cluster ( EKS provider v1.21, Rancher local cluster v2.6.3). For some reason it stucks on
Waiting for API to be available
, in conditions there are
Cluster agent is not connected
event. At the same time AWS console shows that EKS cluster is in
, so basically it means that EKS cluster is running and ready to use. What can the reason of this issue? I understand that
Waiting for API to be available
is to generic issue, but I have no idea where I need to look for the problem. The interesting thing that there is no rancher agents on any of worker nodes. Rancher is accessible from downstream nodes, so connection shouldn’t be an issue here.


05/13/2022, 9:52 PM
Security group issue maybe ?


05/13/2022, 9:56 PM
@careful-piano-35019 I just tried to open all ports for all ipv4 and nothing changed
@careful-piano-35019 any ideas?
Ok, so the problem is that cattle agent on downstream cluster cannot resolve rancher host. I do not see any option how I can specify custom DNS server for downstream EKS cluster. Any ideas?