Skip to content

GitLab Next

Open
Created by Alexander Tanayno@atanaynoDeveloper

It is not possible to configure gitlab-kas to work with grpc without directly editing gitlab-kas deployment

Summary

Our GitLab Kubernetes Agent docs mention that kas-address on the Agent side can be set to wss, ws or grpc scheme. Though when it is set to grpc address like grpc://gitlab-kas.<gitlab-namespace>:5005, the connection fails with code = Unavailable desc = connection closed".

It is possible to make it work via grpc if one edits gitlab-kas deployment and sets --listen-websocket to false but it should be possible to set grpc scheme on gitlab-kas chart via values.yaml

Steps to reproduce

  • follow the doc GitLab Kubernetes Agent and configure Agent to use grpc scheme
  • observe the error in the agent logs: code = Unavailable desc = connection closed"

What is the current bug behavior?

It is not possible to set grpc scheme via gitlab-kas subchart values without modifying gitlab-kas deployment directly.

What is the expected correct behavior?

It should be possible to set grpc scheme via gitlab-kas subchart values.

Additional notes

--listen-websocket=true is currently hardcoded on the chart.