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

[ci.jenkins.io] Set up an ECR pull through cache #4321

Open
Tracked by #4313
dduportal opened this issue Sep 28, 2024 · 0 comments
Open
Tracked by #4313

[ci.jenkins.io] Set up an ECR pull through cache #4321

dduportal opened this issue Sep 28, 2024 · 0 comments
Labels
aws ci.jenkins.io triage Incoming issues that need review

Comments

@dduportal
Copy link
Contributor

dduportal commented Sep 28, 2024

During the last summer, we had to setup a Docker "Pull Through" caching registry in Azure to avoid builds breaking due to HTTP/429 rate limit from DockerHub: #4192 (comment)

Same can be done on AWS with ECR: https://docs.aws.amazon.com/AmazonECR/latest/userguide/pull-through-cache.html

Moving ci.jenkins.io to AWS needs the same kind setup:

  • Registry MUST be private (AWS privatelink) as it cannot be using authentication through Docker Engines (might be solved using EC2 instance identity though)
  • Only DockerHub need to be synced
  • We need for VMs (with Docker CE). Nice to have for the EKS cluster (when autoscaling)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws ci.jenkins.io triage Incoming issues that need review
Projects
None yet
Development

No branches or pull requests

1 participant