Chart v0.68.0 only displays a single runner system id in the UI

We have a our runners setup via helm and set our replicas' to 10. This works fine in v0.67.1, where we see all 10 replica's registered under unique system id's in the UI.

However in v0.68.0 we only see a single runner manager registered in the UI, even though the chart has correctly spun up 10 runners in the cluster, all of which report that they register correctly.

Things I have checked over:

• each runners logs to verify registration is successful ✅
• each runner has picked up jobs successfully ✅
• each runner has correctly picked up the shared configuration ✅
• all runners are using the same runnerToken from the same secret ✅

Please let me know if there's any further information that might help.

I have verified the regression by rolling back to chart v0.67.1, and all runner replicas appear correctly in the UI again.

I could not see any upgrade notes for this release, so may have incorrectly assumed there was no required changes that needed to be made.

values.yaml

# NOTE: Gitlab Runners are installed using terraform with the helm chart.
# 
# Please check:
# https://docs.gitlab.com/ee/ci/runners/new_creation_workflow.html#installing-gitlab-runner-with-helm-chart
#
# for any updated configuration options
#
# NOTE: Current default chart version is v0.67.1

# How many runner pods to launch
replicas: ${replicas}

# The GitLab Server URL (with protocol) that want to register the runner against
gitlabUrl: https://gitlab.com/

# Gitlab Runner Authentication Token
runnerToken: "${auth_token}"

# Unregister runners on termination
unregisterRunners: true

# Maximum number of concurrent jobs
concurrent: 40

# Configuration for the Pods that the runner launches for each new job
runners:
  name: "runner-${name}"
  executor: kubernetes

# Extra Runner configuration provided using environment variables
extraEnv: 
  CACHE_S3_SERVER_ADDRESS: s3.amazonaws.com
  CACHE_S3_BUCKET_NAME: ${s3_bucket}
  CACHE_S3_BUCKET_LOCATION: eu-west-2
  CACHE_SHARED: true
  CACHE_TYPE: s3
  CACHE_PATH: "${s3_path}"

# Do not create Role based Auth for gitlab runners, instead, use a service account
rbac:
  create: false
  
serviceAccount:
  name: "gitlab-runner-jobs"

# Configure integrated Prometheus metrics exporter
metrics:
  enabled: true

# Additional volumeMounts to add to the runner container
volumeMounts:
  - name: runner-cache-volume
    mountPath: /mnt/cache

## Additional volumes to add to the runner deployment
volumes:
  - name: runner-cache-volume
    persistentVolumeClaim:
      claimName: "${s3_path}"