- By: Toni Schmidbauer ( Lastmod: 2021-10-16 )
We had the task of answering various questions related to upgrading Red Hat Quay 3.3 to 3.4 and to 3.5 with the help of the quay-operator.
Thankfully (sic!) everything changed in regards to the Quay operator between Quay 3.3 and Quay 3.4.
So this is a brain dump of the things to consider.
With Quay 3.4 the operator was completely reworked and it basically changed from opinionated to very opinionated. The upgrade works quite well but you have to be aware about the following points:
configHostname, used for providing the quay configuration UI, is no longer configurable
In my test cluster I was using a 10G Ceph block device and the StorageClass did not support volume expansion. So my upgrade stopped at this point and I had to allow volume expansion in the storage class.
With the Quay operator version 3.5 the operator is monitoring all namespaces for custom resources and needs to be installed in the openshift-operators namespace, this is how we upgraded Quay to 3.5 including the operator:
after the Quay upgrade you need to reinstall the operator:
You have to manually cleanup old
Red Hat is working on providing documentation on how to backup and restore Quay in various scenarios. There's an open task for this that provides more information https://issues.redhat.com/browse/PROJQUAY-2242.
Copyright © 2020 - 2023 Toni Schmidbauer & Thomas Jungbauer
Built with Hugo Learn Theme and Hugo