Description:

This is a document issue found when reviewing Quay V3.4 Operator docs.

Docs: https://access.redhat.com/documentation/en-us/red_hat_quay/3.4/html-single/deploy_red_hat_quay_on_openshift_with_quay_operator/index?lb_target=stage 

Issue #1:

In "Chapter 4. Deploying Red Hat Quay", actually Quay Operator require Openshift 4.5 or later

PrerequisitesAn OpenShift 4.2 (or later) 
clusterCluster-scope admin privilege to the OpenShift cluster

Issue #2:

In “4.1. Production deployments”，In Quay V3.4 there' no built-in quay superuser "quay", hence can't specify the password.

Superuser password: Change the default superuser password.

Issue #3:

In “4.1. Production deployments”，In Quay V3.4 customers can't specify the password of config editor, the password was generated by Quay Operator randomly and store in the secret "quay-config-editor-credentials"

Config tool password: Change the Red Hat Quay Config Tool password from the default.

Issue #4:

In “4.1. Production deployments”，In Quay V3.4 customers can't specify Replica count, Memory request and CPU .

Replica count: Based on your expected demand, increase the replica count to set how many instances of the quay container will run.
Memory request: Choose how much memory to assign to the quay container, based on expected demand.
CPU request: Select the amount of CPU you want assigned, based on expected demand.