Red Hat SummitQuesto contenuto non è disponibile nella lingua selezionata.
Chapter 6. Running the upgrade to Red Hat Quay v3.3.4
As noted earlier, once your cluster is running any Red Hat Quay 3.0.z or 3.1.z version, to upgrade your cluster to v3.3.4 you must bring down your entire cluster and make a small change to the configuration before bringing it back up with the 3.3.4 version. Here’s how to do that.
Warning
Once you set the value of DATABASE_SECRET_KEY in this procedure, do not ever change it. If you do, all tokens will need to be regenerated.
- Take all hosts in the Red Hat Quay cluster out of service.
Generate some random data to use as a database secret key. For example:
$ openssl rand -hex 48 2d023adb9c477305348490aa0fd9c
Add a new DATABASE_SECRET_KEY field to your
config.yamlfile. For example:DATABASE_SECRET_KEY: "2d023adb9c477305348490aa0fd9c"
NoteFor an OpenShift installation, the
config.yamlfile is stored as a secret.- Bring up one quay container to complete the migration to v3.3.4.
-
Once the migration is done, make sure the same
config.yamlis available on all nodes and bring up the new quay v3.3.4 service on those nodes. - Start v3.0.z versions of quay-builder and clair to replace any instances of those containers you want to return to your cluster.
