RomanNikitenko

> on the step 2 Generate the che-theia assembly folder the compile.tsconfig.mst.json is created. I believe the name of the file is incorrect - it should be compile.tsconfig.json instead, otherwise...

I'm not sure about using `keycloak` with `7.42` version of Che. Could someone clarify it. maybe @tolusha...

I was able to reproduce the problem **only** for **not** secure connections (a certificate was not provided or is invalid): Another condition to reproduce the issue - `Open Folder` command...

I've changed the title of the issue, please see details in my previous comment.

IMO it's duplicate of https://github.com/eclipse/che/issues/19081

EclipseChe CR ``` apiVersion: org.eclipse.che/v1 kind: CheCluster metadata: creationTimestamp: '2022-09-16T11:57:04Z' finalizers: - checluster.che.eclipse.org - cheGateway.clusterpermissions.finalizers.che.eclipse.org - cheWorkspaces.clusterpermissions.finalizers.che.eclipse.org - namespaces-editor.permissions.finalizers.che.eclipse.org - devWorkspace.permissions.finalizers.che.eclipse.org - dashboard.clusterpermissions.finalizers.che.eclipse.org generation: 5 managedFields: - apiVersion: org.eclipse.che/v2 fieldsType:...

`UBI 8` image uses `1.1.1` version of `openssl` `UBI 9` image uses `3.0.1` version of `openssl` For `che-code` we use `node` that requires `1.1.1` version of `openssl` 

> I would have added a nodejs ubi9 binary in the image and pick-up at runtime the correct nodejs binary. hello, Florent! Agree, it would be good solution and I...

> Another workaround is to pull image locally and copy it to minikube > > ```shell > docker pull ${IMAGE} > docker save "${IMAGE}" > universal-developer-image.tar > eval $(minikube docker-env)...

I noticed the following warnings related to my changes: