Che Code workspace pod restarted due to OOM error in che-code-injector init container

[amisevsk]

Describe the bug

While starting a workspace in OpenShift, I noticed that the workspace pod had to restart due to the che-code-injector init container being OOMKilled. It generally works, but the restart suggests that the memory limit for the init container (currently 128Mi) is right on the edge of being too small.

Che version

next (development version)

Steps to reproduce

(Inconsistent)

1. Start a workspace that uses che-code as the editor
2. Check the containers in the pod for restarts: oc get po <workspace-pod> -o json | jq '.status.initContainerStatuses[] | {name, restartCount}'

Expected behavior

Container should be defined with enough memory to avoid OOMKilled

Runtime

OpenShift

Screenshots

Installation method

OperatorHub

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response