conflicting global registries

[prime shell]

I'm trying to deploy trigger.dev to kubernetes and I have to set the global.imageRegistry to our internal asset proxy. If I set these to our mirror of docker hub everything works other than the webapp and supervisor. It looks like they do not exist on docker hub but do on ghcr.io. If I choose to use our mirror of ghcr.io then everything fails other than the webapp and supervisor. I tried including both our internal registry combined with overriding webapp.image.registry to be ghcr.io as well as supervisor using supervisor.image.registry to ghcr.io but this diid not work as I had hoped.

Is it possible to mix these such that the default docker registry is set with global.imageRegistry but it is overridden for webapp and supervisor?

[obtuse wing]

Hi @prime shell. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

Based on the available knowledge sources, the Trigger.dev Helm chart allows you to override image registry settings for individual components (like webapp and supervisor) by specifying their image tags and registries directly in your custom values file. The documentation shows you can set the image tag for webapp and supervisor, but it does not explicitly document a per-component image registry override (e.g., webapp.image.registry or supervisor.image.registry).

The documented approach for version locking is to set the image tag for each component:

webapp:
  image:
    tag: "v4.0.0"

supervisor:
  image:
    tag: "v4.0.0"

However, there is no explicit mention in the knowledge sources of a webapp.image.registry or supervisor.image.registry field, nor of a way to mix global and per-component registries. The documentation does recommend using an external registry for production and configuring it globally in your values.yaml under the registry section, but does not provide a mechanism for mixing registries for different components within the same deployment. The global registry configuration looks like this:

registry:
  deploy: false
  repositoryNamespace: "your-company"
  external:
    host: "your-registry.example.com"
    port: 5000
    auth:
      enabled: true
      username: "your-username"
      password: "your-password"

Given this, it appears that the current Helm chart does not support mixing image registries at a per-component level (e.g., using a global registry for most images but overriding just webapp and supervisor to use a different registry like ghcr.io). If you need this functionality, you may need to customize the Helm chart or request this feature from the Trigger.dev team.

Summary:
The knowledge sources do not explicitly mention support for per-component image registry overrides in the Helm chart. Only image tags can be set per component, and the registry is set globally. Mixing registries as you described does not appear to be supported out of the box at this time Self-hosting Kubernetes: Configuration Self-hosting Kubernetes: Registry setup Self-hosting Kubernetes: Version locking.

If you need more granular control, you may need to modify the chart or reach out to the Trigger.dev maintainers for guidance.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: