Epic to collect linked issues re: CRW 1.2 to 2.0 migration.

If a customer has already deployed CRW 1.2 and is going to deploy the version 2.0, it should be possible to handle it with an upgrade of CRW:

• The existing user accounts will remain
• The existing configuration (proxies, namespace strategies and other) should remain the same

The workspace being incompatible between CRW 1.x and 2.x, error message will be displayed in the dashboard, pointing to the documentation (on CRW) on how to recreate the workspace in a compliant way for CRW 2.0.

Initial list of tasks:

• no tooling is planned for workspace migration from 6.19.x (1.2) -> 7.x (.2x)
• chectl may support redeployment of che server/operator to an existing namespace (migration/upgrade)
• error messages in Che 7 if Che 6 workspace is loaded

See also CRW-240 re: offline / air gap CRW scenarios/support/docs.

Note too that existing OCP/OSD 4 customers will have to uninstall an existing 1.2 operator subscription before installing the 2.0 subscription. This will NOT destroy any server/db installation; it will simply replace the operator with the new one, and cause container images to be updated based on their existing strategy (rolling update or replace after restart). This also means the CRW 2.0 CSV yaml will NOT be a replaces:1.2 update for previous installations.