This message was deleted.
# randoma
adamant-kite-43734
09/06/2022, 3:29 PMThis message was deleted.
t
tall-school-18125
09/07/2022, 6:47 PMWhen a downstream cluster is set up in Rancher, a kubectl command is run on the downstream cluster which installs the cluster agent. This same command gives the cluster agent a token. The agent then initiates communication with Rancher which is authenticated with that token. I'm not sure if that answers your question
tall-school-18125
09/07/2022, 6:49 PMThe port requirements for Rancher and downstream clusters are here https://rancher.com/docs/rancher/v2.6/en/installation/requirements/ports/
g
gifted-agent-35161
09/09/2022, 6:12 AMThanks for your reply 🙂 . My question was more related to how the local cluster communicates with the downstream one ? I saw many errors on the cluster explorer where the healthcheck could not be checked on the downstream cluster. The cluster API endpoint that been queried was a special port (46634/TCP). But as i read the documentation you provided, it seems that the only port needed is the 6443/TCP.
t
tall-school-18125
09/09/2022, 7:34 PMThe Kubernetes API server runs on 6443. I have no idea where 46634 came from
g
gifted-agent-35161
09/13/2022, 10:22 AMOkay, thanks anyway. I was just wondering about this error. Restarting the rancher container solved the problem.