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

Feature: add an extra endpoint for s3 storage backend #3493

Open
bitsf opened this issue Sep 6, 2021 · 1 comment
Open

Feature: add an extra endpoint for s3 storage backend #3493

bitsf opened this issue Sep 6, 2021 · 1 comment

Comments

@bitsf
Copy link

bitsf commented Sep 6, 2021

When we setup an internal s3 compatible storage backend and want to enable redirect for blobs pulling, registry distribution will use only one endpoint for pulling and pushing, that would make network for pushing. I hope to add a extra endpoint to separate the operation.
The setting can be added in config.yml

storage:
  s3:
     regionendpoint: https://192.168.0.100
     redirectendpoint: https://minio.harbor.xxx.com

or add in redirect section

storage:
  redirect:
     disable: false
     endpoint: https://minio.harbor.xxx.com
  s3:
     regionendpoint: https://192.168.0.100
@wy65701436
Copy link
Collaborator

We can bind these two issues? #3139

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

No branches or pull requests

2 participants