An error occurred while fetching the assigned iteration of the selected issue.
WebSocket timeouts
GKE loadbalancer terminates WebSocket connections after 30 seconds, regardless of whether there is traffic or not.
{"level":"warn","time":"2020-11-17T17:27:08.109+1100","msg":"GetConfiguration.Recv failed","error":"rpc error: code = Unavailable desc = transport is closing"}
{"level":"warn","time":"2020-11-17T17:27:38.357+1100","msg":"GetConfiguration.Recv failed","error":"rpc error: code = Unavailable desc = transport is closing"}
{"level":"warn","time":"2020-11-17T17:28:08.605+1100","msg":"GetConfiguration.Recv failed","error":"rpc error: code = Unavailable desc = transport is closing"}
{"level":"warn","time":"2020-11-17T17:28:38.844+1100","msg":"GetConfiguration.Recv failed","error":"rpc error: code = Unavailable desc = transport is closing"}
{"level":"warn","time":"2020-11-17T17:29:09.088+1100","msg":"GetConfiguration.Recv failed","error":"rpc error: code = Unavailable desc = transport is closing"}
{"level":"warn","time":"2020-11-17T17:29:39.353+1100","msg":"GetConfiguration.Recv failed","error":"rpc error: code = Unavailable desc = transport is closing"}
gitlab-kas
gracefully disconnects agents if a connection is older than 30 minutes (see gitlab-org/cluster-integration/gitlab-agent#63 (closed)), whether it has been used recently or not. This duration is configurable. This issue is about configuring the loadbalancer to have a longer (e.g. +5 minutes) disconnect timeout than connection max age parameter in gitlab-kas
.