此内容没有您所选择的语言版本。

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
    Copy to Clipboard Toggle word wrap
  3. Add a new DATABASE_SECRET_KEY field to your config.yaml file. For example:

    DATABASE_SECRET_KEY: "2d023adb9c477305348490aa0fd9c"
    Copy to Clipboard Toggle word wrap
    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

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat