WORKAROUND:

Run deployment

./deploy.sh -d ...

Waiting for the deployment/codeready-operator to be scaled to 1. Timeout 300 seconds 
...

In another shell:

oc create secret generic rhopp-docker-config --from-file=.dockerconfigjson=/home/rhopp/.docker/config.json --type=kubernetes.io/dockerconfigjson
oc secrets link codeready-operator rhopp-docker-config --for=pull
oc get pods -> oc delete pod <codeready-operator-pod-name> # to force a new pod deployment with the correct secret?

Would a better option be to create the secret and attach it to the operator deployment, rather than having to deploy, patch, and redeploy?

cc: dfestal

Or, if the chectl and operatorhub approaches both work fine, perhaps the solution is to use the correct yaml from the che-operator repo, rather than a variant/hardcoded version here:

https://github.com/redhat-developer/codeready-workspaces-deprecated/blob/6.19.x/operator-installer/deploy.sh#L440-L486

We already do this for these two patches, related to oauth:

https://github.com/redhat-developer/codeready-workspaces-deprecated/blob/6.19.x/operator-installer/deploy.sh#L610-L615

As fetched and patched here:

https://github.com/redhat-developer/codeready-workspaces-deprecated/blob/6.19.x/operator-installer/pom.xml#L84-L107