There is a need to rework the upgrade path job, eg., https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/pre-release/view/OCP%203.11/job/pre-release-upgrading-crw-1.1-to-1.2-OCP/configure

There are two possibilities:
1) Nick will be able to put together upgrade script - in this case, the job should use that.

See https://github.com/redhat-developer/codeready-workspaces-deprecated/pull/28/files for the work in progress

2) Nick will not be able to do that.. .in that case the job should do what we discussed in this thread:

• upgrade operator pod (job is already doing that)
• patch CR with new server image&version (job is already doing that)
• patch CR to use new variable names for keycloak/sso stuff (new thing)
• patch CR to use newer image of sso/postgres (new thing)
• implement verification of sso/postgres pods upgrade to ensure the versions deployed match what's in the operator's spec [1].

[1] https://github.com/eclipse/che-operator/blob/master/pkg/deploy/defaults.go