Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow image Docker registry redefining for the entire package #273

Closed
danil-smirnov opened this issue Sep 22, 2022 · 5 comments · Fixed by #287 or #308
Closed

Allow image Docker registry redefining for the entire package #273

danil-smirnov opened this issue Sep 22, 2022 · 5 comments · Fixed by #287 or #308
Assignees
Labels
enhancement New feature or request

Comments

@danil-smirnov
Copy link

danil-smirnov commented Sep 22, 2022

Why should it be implemented?

In many enterprise environments, image downloads are allowed from internal servers only due to security measurements. Now it's impossible to redefine image registries for all the charts, i.e. nats-io chart lacks this option (nats-io/k8s#378).

Describe the improvement

Ideally it should be a global global.imageRegistry parameter to define it across all the charts, but at least a working image.registry parameter for every chart would help. Maybe all external charts could be adopted and installed from local folders rather than from remote repositories.

Additional context
Add any other context about the problem here if needed.

@vsukhin
Copy link
Contributor

vsukhin commented Sep 22, 2022

Thank you, Danil. Good points!

@vsukhin vsukhin assigned vsukhin and unassigned ypoplavs and vsukhin Sep 27, 2022
@danil-smirnov
Copy link
Author

Hi @vsukhin
I'm afraid this PR does nothing for this issue, as it only creates a secret for a particular registry while images still refer to the public registries and there is no way to redefine them globally.
Also mentioned above external subchart nats still doesn't support a registry parameter.
Because of this, we are unable to use Testkube helm charts in our organization.
Maybe you can check Bitnami charts to learn how to do this properly?

@vsukhin vsukhin reopened this Oct 3, 2022
@vsukhin vsukhin removed their assignment Oct 3, 2022
@vsukhin
Copy link
Contributor

vsukhin commented Oct 3, 2022

Ok, I will reopen this request, we will look at it later

@ypoplavs ypoplavs mentioned this issue Nov 3, 2022
6 tasks
@vsukhin vsukhin added the enhancement New feature or request label Nov 8, 2022
@vsukhin
Copy link
Contributor

vsukhin commented Nov 10, 2022

It's almost done. But we're waiting for changes from NATs, if they implement them. If not, then we need to add thier chart to our repo

@ypoplavs ypoplavs linked a pull request Nov 10, 2022 that will close this issue
6 tasks
@ypoplavs
Copy link
Contributor

ypoplavs commented Dec 8, 2022

Hello @danil-smirnov ,

nats now allows redefining registries per image (not globally yet). Please see the PR: nats-io/k8s#606
So now you can install TK using your own images:

helm install testkube helm-charts/testkube --namespace testkube --create-namespace --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 --set mongodb.global.imageRegistry=REGISTRY_NAME --set global.imageRegistry=REGISTRY_NAME --set preUpgradeHook.enabled=false --set preUpgradeHook.serviceAccount.create=false --debug

nats values define registry for all nats-related images;
mongodb defines mongo registry;
global.imageRegistry defined registry for Testkube-related images.

Also please set --set preUpgradeHook.enabled=false and --set preUpgradeHook.serviceAccount.create=false so that a Mongo upgrade job won’t launch into your cluster. This is used for downgrade Mongo version from 12 to 11 for the users that installed our chart with 12 version earlier.

Please try and let us know about the results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants