1. Stop the Quay and Clair containers.
2. Backup the database and image storage (optional but recommended).
3. Start Clair using the new version of the image.
4. Wait until Clair is ready to accept connections before starting the new version of Red Hat Quay.

Procedure

1. Obtain a list of all Red Hat Quay instances on each system running a Red Hat Quay instance.

   1. Enter the following command on System A to reveal the Red Hat Quay instances:

      $ sudo podman ps

      Copy code to clipboard

      Example output

      CONTAINER ID  IMAGE                                      COMMAND         CREATED        STATUS            PORTS                                        NAMES
      ec16ece208c0  registry.redhat.io/quay/quay-rhel8:v{producty-n1}  registry        6 minutes ago  Up 6 minutes ago  0.0.0.0:80->8080/tcp, 0.0.0.0:443->8443/tcp  quay01

      Copy code to clipboard

   2. Enter the following command on System B to reveal the Red Hat Quay instances:

      $ sudo podman ps

      Copy code to clipboard

      Example output

      CONTAINER ID  IMAGE                                      COMMAND         CREATED        STATUS            PORTS                                        NAMES
      7ae0c9a8b37d  registry.redhat.io/quay/quay-rhel8:v{producty-n1}  registry        5 minutes ago   Up 2 seconds ago   0.0.0.0:82->8080/tcp, 0.0.0.0:445->8443/tcp  quay02

      Copy code to clipboard

   3. Enter the following command on System C to reveal the Red Hat Quay instances:

      $ sudo podman ps

      Copy code to clipboard

      Example output

      CONTAINER ID  IMAGE                                      COMMAND         CREATED        STATUS            PORTS                                        NAMES
      e75c4aebfee9  registry.redhat.io/quay/quay-rhel8:v{producty-n1}  registry        4 seconds ago   Up 4 seconds ago   0.0.0.0:84->8080/tcp, 0.0.0.0:447->8443/tcp  quay03

      Copy code to clipboard

2. Temporarily shut down all Red Hat Quay instances on each system.

   1. Enter the following command on System A to shut down the Red Hat Quay instance:

      $ sudo podman stop ec16ece208c0

      Copy code to clipboard

   2. Enter the following command on System B to shut down the Red Hat Quay instance:

      $ sudo podman stop 7ae0c9a8b37d

      Copy code to clipboard

   3. Enter the following command on System C to shut down the Red Hat Quay instance:

      $ sudo podman stop e75c4aebfee9

      Copy code to clipboard

3. Obtain the latest Red Hat Quay version, for example, Red Hat Quay 3.17, on each system.

   1. Enter the following command on System A to obtain the latest Red Hat Quay version:

      $ sudo podman pull registry.redhat.io/quay/quay-rhel8:{productminv}

      Copy code to clipboard

   2. Enter the following command on System B to obtain the latest Red Hat Quay version:

      $ sudo podman pull registry.redhat.io/quay/quay-rhel8:v{producty}

      Copy code to clipboard

   3. Enter the following command on System C to obtain the latest Red Hat Quay version:

      $ sudo podman pull registry.redhat.io/quay/quay-rhel8:{productminv}

      Copy code to clipboard

4. On System A of your highly available Red Hat Quay deployment, run the new image version, for example, Red Hat Quay 3.17:

   # sudo podman run --restart=always -p 443:8443 -p 80:8080 \
      --sysctl net.core.somaxconn=4096 \
      --name=quay01 \
      -v /mnt/quay/config:/conf/stack:Z \
      -v /mnt/quay/storage:/datastorage:Z \
      -d registry.redhat.io/quay/quay-rhel8:{productminv}

   Copy code to clipboard

5. Wait for the new Red Hat Quay container to become fully operational on System A. You can check the status of the container by entering the following command:

   $ sudo podman ps

   Copy code to clipboard

   Example output

   CONTAINER ID  IMAGE                                      COMMAND         CREATED        STATUS            PORTS                                        NAMES
   70b9f38c3fb4  registry.redhat.io/quay/quay-rhel8:v{producty} registry        2 seconds ago   Up 2 seconds ago   0.0.0.0:82->8080/tcp, 0.0.0.0:445->8443/tcp  quay01

   Copy code to clipboard

6. Optional: Ensure that Red Hat Quay is fully operation by navigating to the Red Hat Quay UI.

7. After ensuring that Red Hat Quay on System A is fully operational, run the new image versions on System B and on System C.

   1. On System B of your highly available Red Hat Quay deployment, run the new image version, for example, Red Hat Quay 3.17:

      # sudo podman run --restart=always -p 443:8443 -p 80:8080 \
         --sysctl net.core.somaxconn=4096 \
         --name=quay02 \
         -v /mnt/quay/config:/conf/stack:Z \
         -v /mnt/quay/storage:/datastorage:Z \
         -d registry.redhat.io/quay/quay-rhel8:{productminv}

      Copy code to clipboard

   2. On System C of your highly available Red Hat Quay deployment, run the new image version, for example, Red Hat Quay 3.17:

      # sudo podman run --restart=always -p 443:8443 -p 80:8080 \
         --sysctl net.core.somaxconn=4096 \
         --name=quay03 \
         -v /mnt/quay/config:/conf/stack:Z \
         -v /mnt/quay/storage:/datastorage:Z \
         -d registry.redhat.io/quay/quay-rhel8:{productminv}

      Copy code to clipboard

8. You can check the status of the containers on System B and on System C by entering the following command:

   $ sudo podman ps

   Copy code to clipboard

Procedure

1. On System B and System C, scale down your Red Hat Quay registry. This is done by disabling auto scaling and overriding the replica county for Red Hat Quay, mirror workers, and Clair if it is managed. Use the following quayregistry.yaml file as a reference:

   apiVersion: quay.redhat.com/v1
   kind: QuayRegistry
   metadata:
     name: registry
     namespace: ns
   spec:
     components:
       …
       - kind: horizontalpodautoscaler
         managed: false
       - kind: quay
         managed: true
         overrides:
           replicas: 0
       - kind: clair
         managed: true
         overrides:
           replicas: 0
       - kind: mirror
         managed: true
         overrides:
           replicas: 0
       …

   Copy code to clipboard

   where:

   managed: false:: Disables auto scaling of Quay, Clair and Mirroring workers overrides:: Sets the replica count to 0 for components accessing the database and objectstorage

   Note

   You must keep the Red Hat Quay registry running on System A. Do not update the quayregistry.yaml file on System A.

2. Wait for the registry-quay-app, registry-quay-mirror, and registry-clair-app pods to disappear. Enter the following command to check their status:

   oc get pods -n <quay-namespace>

   Copy code to clipboard

   Example output

   quay-operator.v3.7.1-6f9d859bd-p5ftc               1/1     Running     0             12m
   quayregistry-clair-postgres-7487f5bd86-xnxpr       1/1     Running     1 (12m ago)   12m
   quayregistry-quay-app-upgrade-xq2v6                0/1     Completed   0             12m
   quayregistry-quay-redis-84f888776f-hhgms           1/1     Running     0             12m

   Copy code to clipboard

3. On System A, initiate a Red Hat Quay upgrade to the latest y-stream version. This is a manual process. For more information about upgrading installed Operators, see Upgrading installed Operators. For more information about Red Hat Quay upgrade paths, see Upgrading the Red Hat Quay Operator.
4. After the new Red Hat Quay registry is installed, the necessary upgrades on the cluster are automatically completed. Afterwards, new Red Hat Quay pods are started with the latest y-stream version. Additionally, new Quay pods are scheduled and started.

5. Confirm that the update has properly worked by navigating to the Red Hat Quay UI:

   1. In the OpenShift console, navigate to Operators → Installed Operators, and click the Registry Endpoint link.

      Important

      Do not execute the following step until the Red Hat Quay UI is available. Do not upgrade the Red Hat Quay registry on System B and on System C until the UI is available on System A.

6. Confirm that the update has properly worked on System A, initiate the Red Hat Quay upgrade on System B and on System C. The Operator upgrade results in an upgraded Red Hat Quay installation, and the pods are restarted.

   Note

   Because the database schema is correct for the new y-stream installation, the new pods on System B and on System C should quickly start.

7. After updating, revert the changes made in step 1 of this procedure by removing overrides for the components. For example:

   apiVersion: quay.redhat.com/v1
   kind: QuayRegistry
   metadata:
     name: registry
     namespace: ns
   spec:
     components:
       …
       - kind: horizontalpodautoscaler
         managed: true
       - kind: quay
         managed: true
       - kind: clair
         managed: true
       - kind: mirror
         managed: true
       …

   Copy code to clipboard

   where:

   kind: horizontalpodautoscaler:: Set this resource to True if the horizontalpodautoscaler resource was set to True before the upgrade procedure, or if you want Red Hat Quay to scale in case of a resource shortage.

Procedure

1. On the OpenShift Container Platform web console, click Operators → Installed Operators → Quay Bridge Operator.
2. Click the Subscription tab.
3. Under Update channel, click stable-3.15 → Save.