Mario Loriedo

I have updated the wireframe and the description.

I have updated the warning text after some a @RickJWagner comment on #21606

Ok but we should not restart the workspace because it has the same name: it may have the same name but refer to another branch (i.e. you have just reviewed...

> Can we just create a new workspace but with another name (maybe adding some suffix) Right but that's what `generateName`, in the DevWorkspace spec, is supposed to do. If...

> I can create a distinct issues for non-samples but in general I would ask the user if he wants to restart the existing workspace or replace it with the...

cc @ibuziuk @dkwon17 @azatsarynnyy

I would use `OPENVSX_REGISTRY_URL` as the name of the env variable. Added the comment to the [CheCluster issue too](https://github.com/eclipse/che/issues/21598#issuecomment-1202249028).

This is great. Thank you @olexii4 for fixing it but I am reopening the issue because if we don't document that https://www.eclipse.org/che/docs/stable/end-user-guide/optional-parameters-for-the-urls-for-starting-a-new-workspace/ nobody will be able to use it.

@karatkep thank you for this issue and the related contribution. Those enhancements were needed to deploy to AKS? And using the instructions in [your repo](https://github.com/karatkep/che-aks-installer) are ment to be used...

@karatkep I have added this issue in [v7.50 release notes](https://github.com/eclipse/che/releases/tag/7.50.0). If you have some instructions on how to deploy Che on Azure AKS please share so that we can make...