Support considerations for Dev Spaces 3.0

DOCS TASK

Ensure 3.0 release notes / support matrix states support in CRW 3.0 is for OCP 4.10 EUS only.

Context

The DevWorkspace Operator 0.9+ requires OpenShift 4.8+ features in its design, which means that it is not installable in an OpenShift 3.11 EUS or 4.6 EUS cluster.

In order to maintain CRW support on OCP 3.11 and 4.6, it's necessary to ensure it's still possible to install/update/deploy CRW on 3.11 and 4.6 once DevWorkspaces support is enabled by default.

Devfile v2.0 features will generally be incompatible with OCP 3.11 and 4.6, as the DevWorkspace Operator is required for handling the underlying DevWorkspace object.

However, since 4.8 has been deemed an EUS release, we won't be supporting OCP 4.6 as of CRW 2.13+.

Support Timelines - see https://cloud.redhat.com/blog/time-is-on-your-side-a-change-to-the-openshift-4-lifecycle:

• OCP 3.11 EUS EOL: June 21 2022
• OCP 4.6 EUS EOL: Oct 2022
• OCP 4.8 EUS EOL: Feb 2023
• OCP 4.10 EUS EOL: Sep 2023

So the plan here is to have 2.15.z releases (if needed) up to the release of 2.16.0, which will end support for existing CRW customers on OCP 3.11 and OCP 4.x up to 4.9.

After June 2022, OCP 3.11 support will end. But support for CRW 2.x in OCP 3.11 and versions up to 4.9 will end when CRW 3.0 occurs.

2.16 will be available on OCP 4.10 EUS only. Once 4.11 is available, support will once again be extended to OCP 4.latest and OCP 4.latest-EUS.

See also CRW-2241, CRW-2571, CRW-2128, CLOUDDST-11685, CLOUDDST-11682