Chapter 15. Geo-replication

Procedure

1. In your Red Hat Quay config editor, locate the Registry Storage section.
2. Click Enable Storage Replication.
3. Add each of the storage engines to which data will be replicated. All storage engines to be used must be listed.

4. If complete replication of all images to all storage engines is required, click Replicate to storage engine by default under each storage engine configuration. This ensures that all images are replicated to that storage engine.

   Note

   To enable per-namespace replication, contact Red Hat Quay support.

5. When finished, click Save Configuration Changes. The configuration changes will take effect after Red Hat Quay restarts.

6. After adding storage and enabling Replicate to storage engine by default for geo-replication, you must sync existing image data across all storage. To do this, you must oc exec (alternatively, docker exec or kubectl exec) into the container and enter the following commands:

   # scl enable python27 bash
   # python -m util.backfillreplication

   Note

   This is a one time operation to sync content after adding new storage.

1. Copy the config.yaml to all machines running Red Hat Quay

2. 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 with the config directory on the host available from $QUAY/config:

   $ sudo podman run -d --rm -p 80:8080 -p 443:8443  \
      --name=quay \
      -v $QUAY/config:/conf/stack:Z \
      -e QUAY_DISTRIBUTED_STORAGE_PREFERENCE=europestorage \
      registry.redhat.io/quay/quay-rhel8:v3.8.15

   Note

   The value of the environment variable specified must match the name of a Location ID as defined in the config panel.

3. Restart all Red Hat Quay containers

Procedure

1. Deploy Quay postgres instance:

   1. Login to the database

   2. Create a database for Quay

      CREATE DATABASE quay;

   3. Enable pg_trm extension inside the database

      \c quay;
      CREATE EXTENSION IF NOT EXISTS pg_trgm;

2. Deploy a Redis instance:

   Note
   • Deploying a Redis instance might be unnecessary if your cloud provider has its own service.
   • Deploying a Redis instance is required if you are leveraging Builders.
   1. Deploy a VM for Redis
   2. Make sure that it is accessible from the clusters where Quay is running
   3. Port 6379/TCP must be open

   4. Run Redis inside the instance

      sudo dnf install -y podman
      podman run -d --name redis -p 6379:6379 redis

3. Create two object storage backends, one for each cluster

   Ideally one object storage bucket will be close to the 1st cluster (primary) while the other will run closer to the 2nd cluster (secondary).

4. Deploy the clusters with the same config bundle, using environment variable overrides to select the appropriate storage backend for an individual cluster
5. Configure a load balancer, to provide a single entry point to the clusters