-
Notifications
You must be signed in to change notification settings - Fork 180
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
Implement Image Syncer Job as GitHub Action #11384
Comments
The're is a agreement between Docker and GIthub: actions/runner-images#1445 (comment) Agreement is already made: actions/runner-images#1445 (comment) |
We've made a decision to define a common location for .yml file with definition of images to sync. The users will not have a way to define their own location. Having files in the same location in every repository using it, will let us collect information for these files or react on changes in the list of images to sync. Implementing such change in the future would require all teams align their tooling and file to common location. |
An |
Description
Migrate the
image-syncer
job from Prow to GitHub Actions by creating a reusable workflow. This migration is necessary to address the issue of exceeding DockerHub's 100 requests per hour limit and to decentralize the maintenance of image synchronization. Each team will manage their ownexternal-images.yaml
file. Detailed instructions will be provided to ensure a smooth transition. The reusable workflow will run on GitHub Actions, leveraging different IP addresses to mitigate rate limit issues.The reusable workflow enables team to use their own secret to access Docker Hub. If no secret is provided, the anonymous download will be used. The credentials to the registry have to be restricted to the reusable workflow and not be shared with the teams.
Reasons
Postponed, as probably dockerhub will not be an issue with GitHub as a runner.
Required to do performance test and decide
Rate Limit Issue: The current Prow-based solution frequently hits DockerHub's 100 requests per hour limit, causing failures.
Acceptance Criteria
Attachments
The text was updated successfully, but these errors were encountered: