Anatolii Bazko

Outdated Jenkins job https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/Che/job/e2e/job/ocp/job/complex/job/disconnected/job/disconnected-deploy/ Related CRW issue https://issues.redhat.com/browse/CRW-2496

@rakeshreddyrg09 It is not possible to specify ingress class separately, but it is possible by setting annotations for ingress: ``` spec: networking: annotations: kubernetes.io/ingress.class: "nginx" nginx.ingress.kubernetes.io/proxy-read-timeout: "3600" nginx.ingress.kubernetes.io/proxy-connect-timeout: "3600" nginx.ingress.kubernetes.io/ssl-redirect:...

@timosur I am not sure if it is needed to both: ``` CHE_OIDC_EMAIL__CLAIM: unique_name CHE_OIDC_USERNAME__CLAIM: unique_name ```

Pls, remove user's namespace before trying a different configuration, since RoleBindings won't be updated automatically.

Currently we have: ```yaml spec: components: dashboard: deployment: headerMessage: show: text: ``` I would put `logo`, `loader`, `styles` into another structure like this: ```yaml spec: components: dashboard: deployment: customization: logo:...

This one https://github.com/eclipse/che/issues/21605

I don't think we can use `registry.redhat.io/openshift4` registry in upstream. But we can switch to `4.8` or even `4.9` in `quay.io/openshift` @amisevsk @sparkoo Do you think it is safe enough...

So, we have to do: 1. Update [1] to [2] & [3] 2. Launch `make update-dev-resources` to propagate these changes to all related resources including olm bundle 3. Spin up...

I faced the same problem. It seems workspace immediately stopped after booting up. DevWorkspace controller log shows: ``` {"level":"info","ts":1658319000.073287,"logger":"controllers.DevWorkspace","msg":"Reconciling Workspace","Request.Namespace":"che-kube-admin-che-x4dl9t","Request.Name":"bash","devworkspace_id":"workspace0256ca635bb144a8"} {"level":"info","ts":1658319000.0918732,"logger":"controllers.DevWorkspace","msg":"Workspace stopped with reason","Request.Namespace":"che-kube-admin-che-x4dl9t","Request.Name":"bash","devworkspace_id":"workspace0256ca635bb144a8","stopped-by":"inactivity"} ``` /cc @dkwon17 Could you have...

After updating operator image, I can't reproduce `The workspace status changed unexpectedly to "Stopped"` error anymore