Quay Operator v3.3.0 Upgrade Procedure #55
Conversation
|
Two notes from a quick glance over it myself:
|
| If your deployment does not specify any specific network-related configuration | ||
| values, this step may not be necessary. Please refer to the documentation to | ||
| ensure that your the configuration options in your current CR are still | ||
| accurate for Quay Operator v3.3.0. |
There was a problem hiding this comment.
when customers read this notes, where can they search and validate the previous CR configurations?
There was a problem hiding this comment.
I changed "ensure that your the" to "ensure that the". As for the CR, I'll leave this for @kurtismullins and keep it open for now.
| certificate may have been created by this process. | ||
|
|
||
| If multiple replicas are needed to scale your Quay registry, it is now safe | ||
| to change the replica count to your desired quantity. |
There was a problem hiding this comment.
pls review is it necessary to let customers know how to update Quay CR file to scale out quay,
for example: suppose the CR name is "demo-quayecosystem", then in order to scale out quay, customers can run "oc edit quayecosystem demo-quayecosystem", change "replicas: 1" to "replicas: 2", or other desired number.
There was a problem hiding this comment.
Done. Fixed content in proc_deploy-quay-openshift-operator.adoc.
|
@kurtismullins I copied this content into a separate section of the "Deploy Quay on OpenShift with Quay Operator" guide. I'm adding the comments from here into that doc. |
|
I'm going to close this PR, since the content and corrections were added to the file proc_deploy-quay-openshift-operator.adoc in PR #56. |
3 participants
This PR is my suggested procedure to update from Quay Operator v1.0.2 to v3.3.0.
It is not written in the correct format, so please do not merge it.
This Pull Requests exists for review and/or re-writing purposes.