As discussed on slack re: RN doc [1]

"For OpenShift 4.0 or 4.1, CodeReady Workspaces 1.2.0 is available today from the OperatorHub. Based on a new operator that leverages the Operator Lifecycle Manager, the installation flow is getting simpler and can be handled without leaving the OpenShift Console. If you already have OpenShift 4.0 or 4.1, get CodeReady Workspaces from the OperatorHub and follow the dedicated documentation."

[1] https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/1.2/html-single/release_notes_and_known_issues/index

• you mention OS 4.0 a lot... which isn't supported with 1.2
• the migration path for existing OS 4.0 customers who want to use CRW 1.2 is: get Openshift (OCP) 4.1, install that, then get a fresh CRW 1.2 install. In theory this would be from the operatorhub / OCP marketplace, but in reality... due to CRW-288... the operator is not yet available there.

So... rhopp@redhat.com dnochevn should we instead tell customers that they can use the deploy.sh script to install CRW 1.2 on OCP 4.1? Is that supported? Tested? Working?