Che Workspaces startup should be frozen when devworkspace is enabled

[sleshchenko]

Is your task related to a problem? Please describe.

Che Workspace and DevWorkspace can't together on the same cluster

Describe the solution you'd like

When devworkspace enabled, Che Workspace can't be started anymore, so:

• Che Workspaces startup should be frozen when devworkspace is enabled;
• Currently, there is no visible difference on left-nav bar, workspace details or workspaces list that workspace is devworkpsace or Che Workspace, the only clue is devfile version in devfile editor. Frozen Che Workspaces should be identified somehow, maybe with special status icon;
• We should guide users to use devworkspaces instead;

[parvathyvr]

The below screens show how we could denote the deprecated Che workspaces.
We could use the 'Alert' icon and when the user hovers,show the tool tip 'Deprecated workspace'.

And when the user clicks on the workspace name and goes to the detailed page-we could show an inline alert which specifies the details and then a action link (eg: link to documentation how they can upgrade the workspace) as shown below.

PS: these are sample screens-we could work on changing the message what the inline alert show.

[ibuziuk]

@l0rd wdyt about the mockups from the previous comment? should we show the che-server-based workspaces and provide relevant docs for migration to devfile v2

[l0rd]

I am +1 for that if that's about less than a week of work. If the estimated effort required is more than that let's skip it.

[max-cx]

Hi, a question to the assignee of this issue:

Will the outcome require any changes to the relevant content of the Installation Guide or Administration Guide or End-user Guide?

Yes/No?

[nickboldt]

Yes, end user experience is impacted by this change and should be updated accordingly.

[ibuziuk]

@l0rd my understanding is that we need to close this issue and open a new one to be aligned with the endgame plan (after migration, workspaces can be restarted without the loss of data persisted in PVs)

[ibuziuk]

Closing in favor of #20845