<p>Few pods in my openshift cluster are still restarted multiple times after deployment.</p>
<p>with describe output:<br />
<code>Last State:     Terminated</code>
<code>Reason:       OOMKilled</code><br />
<code>Exit Code:    137</code></p>
<p>Also, memory usage is well below the memory limits.
Any other parameter which I am missing to check?</p>
<p>There are no issues with the cluster in terms of resources.</p>

dev
<p>„OOMKilled“ means your container memory limit was reached and the container was therefore restarted.</p>
<p>Especially Java-based applications can consume a large amount of memory when starting up. After the startup, the memory usage often drops considerably.</p>
<p>So in your case, increase the ‚requests.limit.memory‘ to avoid these OOMKills. Note that the ‚requests‘ can still be lower and should roughly reflect what your container consumes after the startup.</p>
