Georeplication allows for a single globally-distributed Quay Enterprise to serve container images from localized storage.
When georeplication is configured, container image pushes will be written to the preferred storage engine for that QE instance. After the initial push, image data will be replicated in the background to other storage engines. The list of replication locations is configurable. An image pull will always use the closest available storage engine, to maximize pull performance.
Georeplication requires that there be a high availability storage engine (S3, GCS, RADOS, Swift) in each geographic region. Further, each region must be able to access every storage engine due to replication requirements.
NOTE: Local disk storage is not compatible with georeplication at this time.
Sign in to a super user account and visit
http://yourregister/superuser to view the management panel:
For each machine in each region, add a
QUAY_DISTRIBUTED_STORAGE_PREFERENCE environment variable with the preferred storage engine for the region in which the machine is running.
For example, for a machine running in Europe:
docker run -d -p 443:443 -p 80:80 -v /conf/stack:/conf/stack -e QUAY_DISTRIBUTED_STORAGE_PREFERENCE=europestorage quay.io/coreos/quay:versiontag
NOTE: The value of the environment variable specified must match the name of a Location ID as defined in the config panel