Skip to content

Conversation

@chrisnegus
Copy link
Contributor

Updated the guide for deploying Red Hat Quay on OpenShift using the "Quay Operator" (formerly the Quay Setup Operator). This update included the addition of descriptions for doing post-deployment Quay updates using either the Quay Config Tool or the Quay Operator itself. This update also includes an extensive upgrade description.

@chrisnegus chrisnegus requested a review from thomasmckay May 8, 2020 05:09
@dongboyan77
Copy link

dongboyan77 commented May 9, 2020

In line 764 of proc_deploy-quay-openshift-operator.adoc, Injecting configuration files field. There is an extra string Quay, please remove it, like below:
apiVersion: redhatcop.redhat.io/v1alpha1 kind: QuayEcosystem metadata: name: example-quayecosystem spec: quay: configFiles: - secretName: quayconfigfile files: - key: myprivatekey.pem filename: cloudfront.pem - key: myExtraCaCert.crt type: extraCaCert


. Document all configuration related to your current deployment.
. Copy your CR and modify any configuration values as needed.
. Remove your current deployment using `oc delete -f deployment.yaml`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does deployment.yaml contain? @kurtismullins could you help clarify, thanks

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. I don't know.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My understanding is that's the deployment.yaml file generated during the backup, now it was used to remove the deployment.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, so this assumes that you created a "deployment.yaml" at some point, but this procedure does not show that file being created. Kurtis is on vacation at the moment. I'll have to check with him to find out what he meant. I'll leave this open for the moment.

@chrisnegus chrisnegus changed the title Updated Quay Operator deployment per PROJQUAY-113 Updated Quay Operator deployment per PROJQUAY-334 May 12, 2020
@chrisnegus chrisnegus merged commit 02cde81 into quay:master May 12, 2020
chrisnegus pushed a commit that referenced this pull request May 12, 2020
* Updated Quay Operator deployment per PROJQUAY-113

* Included more QE comments per PR #56, PROJQUAY-334

* Editing pass for typos
stevsmit pushed a commit that referenced this pull request Apr 15, 2025
* Updated Quay Operator deployment per PROJQUAY-113

* Included more QE comments per PR #56, PROJQUAY-334
stevsmit pushed a commit that referenced this pull request Apr 15, 2025
* Updated Quay Operator deployment per PROJQUAY-113

* Included more QE comments per PR #56, PROJQUAY-334

* Editing pass for typos
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants