fix: Add topology service volume mounts to sidekiq main container

Tarun Khandelwalrequested to merge
fix/sidekiq-topology-service-mounts into master

Problem

The sidekiq deployment was missing explicit volume mounts for topology service TLS certificates in the main container, causing gRPC connection failures when attempting to connect to the topology service.

Root Cause

While the topology service secrets were being mounted at /etc/gitlab in the sidekiq-secrets volume, the GitLab application configuration expects them at /srv/gitlab/config/topology-service/. This path mismatch resulted in the application being unable to locate the required TLS certificates (tls.crt and tls.key).

Error Observed 

GRPC::Unavailable (status code 14)

This error occurs when the topology service client attempts to establish connections but cannot find the required TLS certificates at the expected path.

Current State

  • Main sidekiq container: ❌ Missing topology service volume mounts

References

This brings Sidekiq in line with other components (webservice, toolbox, migrations) that already use this helper in their main containers.

part of: gitlab-com/gl-infra/tenant-scale/cells-infrastructure/team#598 (closed)

Edited by Tarun Khandelwal

Merge request reports