Helm chart: missing image registry key

[andreas-mueller-bb]

Describe the bug
Opened the issue here, as the helm chart repo does not support opening one.
(https://github.com/HumanSignal/charts)

To Reproduce
Steps to reproduce the behavior:

1. Try to specify image registry via global.image.registry
2. get error "global.image: Additional property registry is not allowed"

Expected behavior
Be able to set image registry explicitly.

Environment (please complete the following information):

• OS: Kubernetes
• Label Studio Helm Chart 1.9.0

[heidi-humansignal]

Hello,

Thank you for contacting Label Studio,

The issue occurs because our Helm chart schema doesn’t currently support a separate registry key under global.image. Instead, you can specify the entire image path (including your registry domain) within the repository field. For example:

global: image: repository: myregistry.mycompany.com/heartexlabs/label-studio tag: "1.14.0"

This approach ensures that Helm recognizes the custom registry path as part of the repository. If you also need credentials for a private registry, you can configure global.imagePullSecrets accordingly.

We appreciate the feedback on trying to define registry separately. We’ll note this as a feature request for future improvements. If you have any more questions or run into further issues, please let us know!

Comment by Oussama Assili
Workflow Run

[heidi-humansignal]

Hello,

I am following up on the previous email I have sent. we will be introducing the capabilities to add Registry to our Helm Config starting from Version 1.9.1

Thanks for bringing this up!

Comment by Oussama Assili
Workflow Run

[andreas-mueller-bb]

Thank you so much for your fast replies both the suggested workaround as well as implementing as a new capability in the next version! :)

[heidi-humansignal]

You are very welcome!

Please feel free to contact us if you have additional requests or questions, we are happy to assist you!

Have a lovely day!

Comment by Oussama Assili
Workflow Run