Andrew O.

> Hello @AObuchow I believe (correct me if I am wrong) che operator must take care of some specific things related to Che and not to be the operator which...

> but the alternative might be simpler for consumers and simpler to implement on our side (since I don't think we would need to make a new field in the...

> @tolusha @AObuchow Is it safe to replace `defaults.ConfigAnnotationEndpointName` to `dwconstants.DevWorkspaceEndpointNameAnnotation` everywhere in the che operator? Since existing routes will have their annotations updated by the solver on workspace start,...

A quick [search](https://github.com/search?q=org%3Aeclipse-che%20%22endpoint-name%22&type=code) seems to show that only Che Operator and the Che Devfile registry (which is now deprecated IIRC?) use the `che.routing.controller.devfile.io/endpoint-name` annotation. A similar [search](https://github.com/search?q=org%3Aeclipse-che+%22component-name%22&type=code) for the `che.routing.controller.devfile.io/component-name`...

@tolusha After further consideration, I think having the Che Router add the devfile endpoint annotations would make sense and is the cleanest approach. One could argue the Che Router is...

A customer has encountered a variant of this same bug. In the customer's case, they had a parent devfile that defines a starterProject as well as devfile commands that are...

@jhadvig is it possible to have this backport merged? It would help a lot with the QE testing for the upcoming Web Terminal 1.11 release. Thank you :)

If you're running Che on Kubernetes (and not OpenShift), then I suspect you're encountering https://github.com/eclipse-che/che/issues/23179 (which has some workarounds provided in the issue). This bug only occurs when you're not...

From the Che Dashboard, you can provide an image for your workspace. Try using `quay.io/devfile/universal-developer-image:ubi9-latest` and then selecting your devfile sample. This should hopefully be a workaround, but the UDI...

@eye0fra Thank you for reporting this. For what its worth, this is an internally known DWO issue that's currently only documented as a [TODO](https://github.com/devfile/devworkspace-operator/blob/ff723835cc3ed38c9f8a5fbf36dcfddf1890ac9c/controllers/controller/devworkspacerouting/solvers/common.go#L49). I'm not sure if there's any...