-
Notifications
You must be signed in to change notification settings - Fork 1.2k
ci: publish images to GitHub Container Registry too #4846
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
Conversation
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Welcome @medyagh! It looks like this is your first PR to volcano-sh/volcano 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR extends the CI/CD pipeline to publish Docker images to GitHub Container Registry (ghcr.io) in addition to Docker Hub, addressing rate limiting concerns for minikube integration tests.
- Adds authentication step for GitHub Container Registry using built-in
GITHUB_TOKEN - Introduces a parallel release workflow that pushes images to both Docker Hub and ghcr.io
- Updates logout procedure to cleanly disconnect from both registries
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@medyagh Please make the DCO check happy |
7720db8 to
8f1d352
Compare
|
/ok-to-test |
done :) |
|
@hzxuzhonghu I think the project admins would need to enable the "github packages" in the repo to make it work |
hzxuzhonghu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
|
github packages has been enabled and used by another sub project |
hajnalmt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea! I encountered rate limiting issues with Docker hub too.
I had some minor comments, please address them plus squash your commits too!
|
Hi, thanks for your contribution, could you squash your commits? This will help us organize the release notes and allow others easier to track your modifications |
Signed-off-by: Medya Ghazizadeh <medya@google.com>
done |
hajnalmt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Thank you for the change!
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hajnalmt, hzxuzhonghu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
publishes docker images into github ctonainer registry in addition to docker.io
What this PR does / why we need it:
in order to comply with minikube integration test requirements and not be rate limited by docker.io
Which issue(s) this PR fixes:
closes #4845
Fixes #
Special notes for your reviewer:
To keep volcano integration tests with minikube it is required to be publishing images somwhere with no rate limit
Does this PR introduce a user-facing change?
related kubernetes/minikube#22076