global.imageRegistry is not taken into account for all images about helm-charts HOT 7 CLOSED

Miss from our side. We will update the docs. Apologies for the inconvenience @sylock !

from helm-charts.

hi @sylock! Thank you for offer, however I have already updated the docs. Could you please take a look and give your feedback: https://docs.testkube.io/articles/deploying-from-private-registries?
If there is something missing, please feel free to submit a PR with changes :)

from helm-charts.

thank you @sylock please take a look at it @ypoplavs

from helm-charts.

Hello @sylock!
NATS is a third-party chart that we rely on and, therefore, it requires passing image registry differently than in Testkube. You can use --set or provide the image registries in values.yaml file. Example of using --set:

--set nats.nats.image.registry=REGISTRY_NAME --set nats.natsbox.image.registry=REGISTRY_NAME  --set nats.reloader.image.registry=REGISTRY_NAME  --set nats.exporter.image.registry=REGISTRY_NAME

from helm-charts.

ok. If it is the expected behavior, I would suggest to explain it somewhere in the helm documentation (like How to install testkube off of the internet ?).

from helm-charts.

If I can help tell me what/where. I can make a change proposal to the doc (but please give me some guidelines).

from helm-charts.

Hello @ypoplavs I've tested the new documentation in a disconnected cluster and that works now if we additionally set the registry for nats. Thanks!

from helm-charts.