<p>I am using a containerized Spring boot application in Kubernetes. But the application automatically exits and restarts with exit code 143 and error message &quot;Error&quot;.</p>
<p>I am not sure how to identify the reason for this error.</p>
<p>My first idea was that Kubernetes stopped the container due to too high resource usage, as described <a href="https://komodor.com/learn/exit-codes-in-containers-and-kubernetes-the-complete-guide/" rel="noreferrer">here</a>, but I can't see the corresponding kubelet logs.</p>
<p>Is there any way to identify the cause/origin of the <code>SIGTERM</code>? Maybe from spring-boot itself, or from the JVM?</p>

<blockquote>
<p>Exit Code 143</p>
</blockquote>
<ol>
<li><p>It denotes that the process was terminated by an <code>external signal</code>.</p>
</li>
<li><p>The number 143 is a sum of two numbers: 128+x, <code># where x is the signal number sent to the process that caused it to terminate.</code></p>
</li>
<li><p>In the example, x equals 15, which is the number of the <code>SIGTERM</code> signal, meaning the process was killed forcibly.</p>
</li>
</ol>
<p>Hope this helps better.</p>
