Gitlab 11.3 introduced Web Terminals for Gitlab CI jobs - a feature we’re really excited about.
Unfortunately from the documentation it is not clear how exactly this feature is to be setup when running on gitlab.com and using a self-hosted runner.
The documentation mentions the session_server section in gitlab CI has to be configured: https://gitlab.com/gitlab-org/gitlab-runner/blob/master/docs/configuration/advanced-configuration.md#the-session_server-section . However it is unclear to which values listen_address and advertise_address should be set when using gitlab.com together with self-hosted runners on kubernetes/gke and having the whole setup secured (i.e. no external party can connect to web terminals running in our self-hosted k8s cluster).
For context this is the current setup we use:
- gitlab.com in Silver Plan
- gitlab-runner setup on GKE via gitlab runner helm chart and registered as group runner (https://docs.gitlab.com/ee/install/kubernetes/gitlab_runner_chart.html)
- all ci jobs of our private repos run on that group runner
Does anyone know what to set as listen_address / advertise_address and how the endpoint would be secured?