Cluster side KAS setup : "error handling a connection"

Hello,

I have the following setup on my PC,

While installing KAS agent, I was offered a Recommended installation using kubectl. I could run it on my PC with minikube to get the gitlab-agent running in the cluster. However, the logs are filled with the following messages,

{"level":"error","time":"2021-12-24T09:37:14.669Z","msg":"Error handling a connection","mod_name":"reverse_tunnel","error":"Connect(): rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing failed to WebSocket dial: failed to send handshake request: Get \\\"https://gitlab.example.com/-/kubernetes-agent\\\": dial tcp 172.17.0.2:443: connect: connection refused\""}
{"level":"error","time":"2021-12-24T09:37:22.986Z","msg":"Error handling a connection","mod_name":"reverse_tunnel","error":"Connect(): rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing failed to WebSocket dial: failed to send handshake request: Get \\\"https://gitlab.example.com/-/kubernetes-agent\\\": dial tcp 172.17.0.2:443: connect: connection refused\""}
{"level":"warn","time":"2021-12-24T09:37:24.493Z","msg":"GetConfiguration failed","error":"rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing failed to WebSocket dial: failed to send handshake request: Get \\\"https://gitlab.example.com/-/kubernetes-agent\\\": dial tcp 172.17.0.2:443: connect: connection refused\""}

Naturally, the connection status of the KAS agent on GitLab remains Never connected.

Any help would be much appreciated. Thank you.

1 Like

Same problem, but using wss:// not https://
Same results in logs. Gitlab-ce 14.6.0