Applying a global configuration (ConfigMap, Secret, Template) causes all running workspaces to immediately restart.

Is your enhancement related to a problem? Please describe

When a Dev Spaces administrator creates or modifies a global configuration that creates ConfigMaps, Secrets, Quotas, or other objects in user namespaces, all running workspaces are immediately restarted.

To the users this looks like a brief outage as there is no warning.

Describe the solution you'd like

Ideally, the change would be applied on the next workspace start.

Perhaps a dialog to let the user know that there is a config change and their workspace should be restarted.

Describe alternatives you've considered

No response

Additional context

No response

Related issue https://github.com/eclipse-che/che/issues/22522#issuecomment-1743168958

Hello @cgruver Unfortunately, I don’t see a feasible way to implement this — there are some technical limitations that cannot be overcome. The main problem here is that even if we mount the resources (marked with special attributes) only when the workspace starts—and not while it’s running—we still need to decide how to handle changes to those resources while the workspace is active. The crucial question is how we can prevent the workspace from restarting when those resources are modified, since the source object differs from the one in the cluster.

What I can suggest is to mark the entire workspace to indicate that it shouldn’t restart when automount resources changed.

cc @dkwon17 cc @ibuziuk