Hi everyone, I have three clusters managed by Rancher that use fleet. If I go into the continuous delivery tab, under clusters, i see that two of them are in Wait Check-In state with the error

Get "<https://172.18.33.123/k8s/clusters/c-sthmh/version?timeout=15s>": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

. I went looking for the fleet-controller log in the upstream cluster, and i see that it also says

level=error msg="error syncing 'fleet-default/c-sthmh': handler import-cluster: Get \"<https://172.18.33.123/k8s/clusters/c-sthmh/version?timeout=15s>\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers), requeuing"

To try and understand what's going on, i tried to launch a

kubectl get services --all-namespaces

, and from the results of that check I can see that there is no pod with the clusterIP mentioned in the error. Who should the fleet-controller contact at that ip? The rancher pod? The thing I don't get is that one of the three clusters works fine with fleet and doesn't have any problem. Does someone know what could be going on?