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

private registry docs should be clear about what images are required #428

Open
kwmonroe opened this issue Jul 8, 2020 · 0 comments
Open
Assignees

Comments

@kwmonroe
Copy link
Contributor

kwmonroe commented Jul 8, 2020

We've had a few pings from users that would like to use a private registry for some images and a public one for others. E.g. a user has a custom app they want to deploy in k8s that is only hosted in their registry, but they want all other images coming from rocks/dockerhub/gcr.io/etc.

At the moment, if a user specifies a private registry with the image-registry config option, we require all images be in that registry. We should make that clear in our docs.

Edit: See #237 for the somewhat related issue requesting better instructions for mirroring rocks images to a private registry. If users can batch-pull from rocks and batch-push to their own registry, I think that'll be a viable workaround until we support the private/upstream registry workflow.

@evilnick evilnick self-assigned this Jul 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants