i hava deploy harbor in guangzhou 、shanghai、 singapore, use oss storage
deploy architecture:
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.
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?
i hava deploy harbor in guangzhou 、shanghai、 singapore, use oss storage deploy architecture:
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.
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?