Enable Topology Service client for gitlab-shell on gprd-cny (phase 1/4)

What

Phase 1 of 4 of the Cells SSH routing rollout (gitlab-com/gl-infra/production#22944): enables the Topology Service gRPC client for gitlab-shell on gprd-cny (8 pods, low-volume canary).

gitlab:
  gitlab-shell:
    config:
      topologyService:
        enabled: true
        cellEndpoint:
          scheme: https
          port: 443

The block goes into the per-environment file releases/gitlab/values/gprd-cny.yaml.gotmpl, not gprd.yaml.gotmpl, so only this cluster is affected. That file is layered after gprd.yaml.gotmpl and deep-merged, so the existing gitlab-shell.config keys (loginGraceTime, proxyProtocol) are kept. The address and mTLS settings come from the existing global.appConfig.cell.topologyServiceClient in gprd.yaml.gotmpl (topology-grpc.runway.gitlab.net:443, cell-1-production-mtls-cert).

It's the same configuration as staging (!5836 (merged), validated in gitlab-org/gitlab-shell#864 (closed) and gitlab-org/gitlab-shell#874).

When to merge

Warning

Do not merge outside the change window. Merge only as the "Phase 1" step of gitlab-com/gl-infra/production#22944, after every prerequisite there is complete. P1, the Cloudflare body-buffering rule for */ssh-upload-pack and */ssh-receive-pack on the gitlab.com zone, is the most important. Without it every non-trivial clone fails at ~15s.

Soak after rollout: 30 min. Success criteria and rollback triggers are in the change request.

Rollback

Merge the pre-created revert MR for this phase (!5881 (closed)). It targets this branch until this MR merges, then GitLab retargets it to master.


🤖 Created with the help of OpenCode Duo

Edited by Vladimir Glafirov

Merge request reports

Loading
Loading