Florent BENOIT

Ok could you try to find machine exec process, kill it and restart it ( with the same options) Get it using `ps auxwwww`

ok I don't know how it's affecting the process :-/ but at least there is one clue about it

There used to be branches like `1.62.x`, `1.63.x` with `stable` releases of VS Code and the job is cutting release and pushing images etc https://github.com/che-incubator/che-code/blob/main/.github/workflows/image-publish-stable.yml I think we should map...

I still don't know why the lifecycle of Che should be used in CheCode I expect as a user to have a VS Code v1.71.0, not a VS Code 7.54.0

cc @svor

@Divine1 it might be interesting as well if you could provide the raw kubernetes metrics for this pod (so we can see how it's reported)

Hello @tianlinzx If you're talking about "integrating the IDE" you should add an editor there https://github.com/eclipse-che/che-plugin-registry/blob/main/che-editors.yaml It'll require a OCI image available and declaring ports/volumes etc

on ubi9 there are different libcrypto versions ``` /usr/lib64/libcrypto.so.3.0.1 /usr/lib64/libcrypto.so.3 ```

so maybe copying nodejs binary from `ubi9/nodejs-16` in addition to `ubi8` or we grab a nodejs binary with a different openssl version

I would have added a nodejs ubi9 binary in the image and pick-up at runtime the correct nodejs binary. if ssl 1.1, pick-up nodejs from ubi8 else if ssl 3,...