feat(dind): multi-queue support and Docker mode fixes

[michaellzc]

related https://github.com/sourcegraph/sourcegraph/pull/12881

Summary

• Add queues list to values: when set, renders one Deployment per queue instead of the single executor Deployment; each queue merges with global executor.env (queue overrides global) and supports replicaCount and resources overrides
• Add executor.resources global and per-queue resources override for the executor container
• Fix readiness probe path from /ready (404) to /healthz — the health server only exposes /healthz
• Set EXECUTOR_USE_KUBERNETES=false to prevent the executor from auto-detecting Kubernetes mode via KUBERNETES_SERVICE_HOST/PORT (always injected into pods); requires executor image with EXECUTOR_USE_KUBERNETES flag support (sourcegraph/sourcegraph@e87902b)
• Set enableServiceLinks: false to reduce env noise in pods
• Fix private docker registry image (docker/registry:2 → registry:3)

Test plan

• Deployed to dev cluster with both batches and codeintel queues
• Verified executors are running in Docker mode (no RBAC errors)
• helm template renders correctly for both multi-queue and single-deployment modes

storageClass:
  create: false
  name: sourcegraph

sourcegraph: 
  image:
    repository: us-docker.pkg.dev/sourcegraph-images/external
    defaultTag: docker-images-notest-06-03-fix_374565_2026-06-04_7.3-e87902b59ff0
    useGlobalTagAsDefault: true

executor:
  replicaCount: 4
  env:
    # -- The external URL of the Sourcegraph instance. Required.
    EXECUTOR_FRONTEND_URL:
      value: "http://frontend.sourcegraph.internal"
    # -- The shared secret configured in the Sourcegraph instance site config under executors.accessToken. Required.
    EXECUTOR_FRONTEND_PASSWORD:
      value: <redacted>

queues:
  - name: batches
    replicaCount: 4
    env:
      EXECUTOR_QUEUE_NAME:
        value: batches
  - name: codeintel
    replicaCount: 4
    env:
      EXECUTOR_QUEUE_NAME:
        value: codeintel

🤖 Generated with Claude Code

[marcleblanc2]

This syntax seems awkward to operate (easier to get wrong than to get right for a new customer's junior admin)

queues:
  - name: batches
    replicaCount: 4
    env:
      EXECUTOR_QUEUE_NAME:
        value: batches
  - name: codeintel
    replicaCount: 4
    env:
      EXECUTOR_QUEUE_NAME:
        value: codeintel

If possible, this would be simpler:

queues:
  batches:
    replicaCount: 4
  codeintel:
    replicaCount: 4

Or this, if either queue can use the same number of replicas

queues:
  batches:
  codeintel:

[marcleblanc2]

Actually, to help reduce the transition cost of moving customers from the k8s Helm chart to this one, it'd be ideal if this Helm chart could read the same values from an override file which was successful with the k8s Helm chart @michaellzc

[marcleblanc2]

Some examples here: https://sourcegraph.sourcegraph.com/search?q=repo:%5Egithub%5C.com/sourcegraph/customer-assets$+lang:YAML+%5Eexecutor:$&patternType=regexp&sm=0

Also to note, it's common to use one Helm values override.yaml file when deploying multiple of our Helm charts, so the values which get read from multiple charts don't need to be maintained in duplicate in separate override files.

[marcleblanc2]

Left comments in the PR thread re: ergonomics of using the added YAML syntax; it looks easier to get wrong than it is to get right, especially for some of our self-hosted customer admins.