SupportConsoleDevelopersStart a trialContact

Chapter 6. Running the upgrade to Red Hat Quay v3.2.2

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.2.2 you must bring down your entire cluster and make a small change to the configuration before bringing it back up with the 3.2.2 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.

  1. Take all hosts in the Red Hat Quay cluster out of service.

  2. Generate some random data to use as a database secret key. For example: 

    $ openssl rand -hex 48
2d023adb9c477305348490aa0fd9c

  3. Add a new DATABASE_SECRET_KEY field to your config.yaml file. For example: 

    DATABASE_SECRET_KEY: "2d023adb9c477305348490aa0fd9c"
    Note

    For an OpenShift installation, the config.yaml file is stored as a secret.

  4. Bring up one quay container to complete the migration to v3.2.2.
  5. Once the migration is done, make sure the same config.yaml is available on all nodes and bring up the new quay v3.2.2 service on those nodes.
  6. Start v3.2.2 versions of quay-builder and clair to replace any instances of those containers you want to return to your cluster.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.