goharbor / harbor

An open source trusted cloud native registry project that stores, signs, and scans content.
https://goharbor.io
Apache License 2.0
22.97k stars 4.64k forks source link

how to fix back to source question #20669

Open z7658329 opened 4 days ago

z7658329 commented 4 days ago
  1. i hava deploy harbor in guangzhou 、shanghai、 singapore, use oss storage deploy architecture:

    image
  2. my scenario is as follows: first, images between harbors are synchronized using the harbor replication function. when a user built an image in Guangzhou, the image will be pushed to the harbor in Guangzhou . By default, pull/push image to harbor is parsed nearby.

  3. my question is : when user's application needs to be deploy in Shanghai, it will pull image from Shanghai harbor, if the replication of Guangzhou harbor to Shanghai is slow, then Shanghai harbor will return 404 not found, so how to go back to the source to Guangzhou harbor? dose harbor Indicates whether to configure the source back?

z7658329 commented 3 days ago

any one can answer me ? thanks @ctrlaltdel @jessehu @edevil @fsword

MinerYang commented 33 minutes ago

Have you tried set a proxy-cache project in your ShangHai instance? And which version of harbor you are using?