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

feat(k8s): allow using registry mirror for utility images #6552

Merged
merged 1 commit into from
Oct 21, 2024

Conversation

eysi09
Copy link
Collaborator

@eysi09 eysi09 commented Oct 16, 2024

What this PR does / why we need it:

Garden uses various utility container images, e.g. for the K8s sync utility pod, and hosts them on Docker Hub.

Some users have their own mirror of Docker Hub that they'd rather use instead of Docker Hub itself. This avoids issues with rate limiting among other things.

This commit adds a config field on the Kubernetes provider spec that allows users to configure what registry is used.

Note that it only allows users to specify the registry domain, not the repository, image name, or tag. So the assumption is that mirror has the exact same "layout" as Docker Hub itself which is usually (always?) the case.

If needed, we can later expose more granular control, e.g. setting the image tag, but that's not required for now.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

@eysi09 eysi09 force-pushed the allow-registry-mirror branch 9 times, most recently from c452a78 to 05e717d Compare October 16, 2024 13:48
@eysi09 eysi09 changed the title feat(k8s): allow using registry mirror for utility images (WIP) feat(k8s): allow using registry mirror for utility images Oct 16, 2024
@eysi09 eysi09 marked this pull request as ready for review October 16, 2024 13:49
@eysi09 eysi09 force-pushed the allow-registry-mirror branch from 05e717d to c146062 Compare October 16, 2024 14:06
@eysi09 eysi09 enabled auto-merge October 16, 2024 14:07
@eysi09 eysi09 requested review from twelvemo and stefreak October 16, 2024 14:07
Garden uses various utility container images, e.g. for the K8s sync
utility pod, and hosts them on Docker Hub.

Some users have their own mirror of Docker Hub that they'd rather use
instead of Docker Hub itself. This avoids issues with rate
limiting among other things.

This commit adds a config field on the Kubernetes provider spec that
allows users to configure what registry is used.

Note that it only allows users to specify the registry domain, not the
repository, image name, or tag. So the assumption is that mirror has the
exact same "layout" as Docker Hub itself which is usually (always?) the
case.

If needed, we can later expose more granular control, e.g. setting the
image tag, but that's not required for now.
@eysi09 eysi09 force-pushed the allow-registry-mirror branch from da03f3c to 42178fe Compare October 16, 2024 17:02
Copy link
Collaborator

@twelvemo twelvemo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great stuff. Love the FAQ!

@eysi09 eysi09 added this pull request to the merge queue Oct 18, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 18, 2024
@eysi09 eysi09 added this pull request to the merge queue Oct 18, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 18, 2024
@vvagaytsev vvagaytsev added this pull request to the merge queue Oct 21, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 21, 2024
@vvagaytsev vvagaytsev added this pull request to the merge queue Oct 21, 2024
Merged via the queue into main with commit 122371d Oct 21, 2024
42 checks passed
@vvagaytsev vvagaytsev deleted the allow-registry-mirror branch October 21, 2024 06:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants