<p>This question is about logging/monitoring.</p>
<p>I'm running a 3 node cluster on AKS, with 3 orgs, Dev, Test and Prod. The chart worked fine in Dev, but the same chart keeps getting killed by Kubernetes in Test, and it keeps getting recreated, and re-killed. Is there a way to extract details on why this is happening? All I see when I describe the pod is Reason: Killed</p>
<p>Please tell me more details on this or can give some suggestions. Thanks!</p>

<p>There might be various reasons for it to be killed, e.g. not sufficient resources or <a href="https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes" rel="nofollow noreferrer">failed liveness probe</a>.</p>
<p>For SonarQube there is a <a href="https://github.com/helm/charts/blob/7e45e678e39b88590fe877f159516f85f3fd3f38/stable/sonarqube/templates/deployment.yaml#L205" rel="nofollow noreferrer">liveness and readiness probe</a> configured so it might fail. Also as described in <a href="https://github.com/helm/charts/blob/7e45e678e39b88590fe877f159516f85f3fd3f38/stable/sonarqube/values.yaml#L79" rel="nofollow noreferrer">helm's chart values</a>:</p>
<blockquote>
<p>If an ingress <em>path</em> other than the root (/) is defined, it should be reflected here<br />
A trailing &quot;/&quot; must be included</p>
</blockquote>
<p>You can also check if there are sufficient resources on node:</p>
<ul>
<li>check what node are pods running on: <code>kubectl get pods -test</code> and
then run <code>kubectl describe node &lt;node-name&gt;</code> to check if there is no
disk/ memory pressure.</li>
</ul>
<p>You can also run <code>kubectl logs &lt;pod-name&gt;</code> and <code>kubectl describe pod &lt;pod-name&gt;</code> that might give you some insight of kill reason.</p>
