Geo: Topology service fails to start on secondary due to port 9090 conflict with primary

Overview

On a Geo secondary instance, the topology service fails to start because it attempts to bind to port 9090, which is already in use by the topology service running on the primary instance.

Impacted categories

The following categories relate to this issue:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Steps to replicate (optional)

On a Geo GDK, run gdk start on the secondary GDK, then gdk status to check the services: notice that the topology service is down, wanting up.

Proposal (optional)

Disable the topolody service in the secondary with:

gitlab:
  cell:
    topology_service_client:
      enabled: false
gitlab_http_router:
  gitlab_rules_config: passthrough
gitlab_topology_service:
  enabled: false

Environment (optional)

• Operating system name: <!-- output of `uname -a` command -->
• Architecture: <!-- output of `arch` or `uname -m` command -->
• The contents of your gdk.yml (if any)
• Ruby version: <!-- output of `ruby --version` command -->
• GDK version: <!-- output of `git rev-parse --short HEAD` command -->