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

Support project auto sync feature by pull-based replication mode #15060

Closed
wants to merge 1 commit into from

Conversation

yunkunrao
Copy link
Contributor

@yunkunrao yunkunrao commented Jun 4, 2021

Signed-off-by: yunkunrao yunkunrao@gmail.com

Summary

This PR adds event-based trigger mode for pull-based replication mode. This PR is related with #14736 .

Background

Briefly, current replication policy doesn't support event-based trigger mode for pull-based replication mode.
And alternative solution proxy cache seems to have a similar function, but it has it's own limitation that docker image namespace has to be changed with a new proxy cache project as the prefix.

Solution

Harbor admin can create a project with the same project name as the upsteam Harbor's project name with specified upstream registry_id and enable auto sync option.

When client run the docker pull cmd, local harbor will synchronize the docker image automically in the project. In other words it's totally transparent to docker client without any prefix in docker image full name.

For example, if we want to pull the latest image from downstream Harbor

  • For proxy cache, we can run docker pull <downstream_harbor:port>/proxy/<your ns>/<your image>:latest
  • For pull-based replication mode, we can run docker run <downsteam_harbor:port>/<your ns>/<your image>:latest. Only prerequisites are project name should be the same as upstream's project name and project enable auto-synced option.

Signed-off-by: yunkunrao <yunkunrao@gmail.com>
@yunkunrao
Copy link
Contributor Author

Proposal was submitted, please refer to goharbor/community#169

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Apr 16, 2022
@github-actions
Copy link

github-actions bot commented Jul 5, 2022

This PR was closed because it has been stalled for 30 days with no activity. If this PR is still relevant, please re-open a new PR against main.

@github-actions github-actions bot closed this Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants