<p>Our Pods usually spend at least a minute and up to several minutes in the <code>Pending</code> state, the events via <code>kubectl describe pod x</code> yield:</p>
<pre><code>Events:
  Type    Reason     Age        From               Message
  ----    ------     ----       ----               -------
  Normal  Scheduled  &lt;unknown&gt;  default-scheduler  Successfully assigned testing/runner-2zyekyp-project-47-concurrent-0tqwl4 to host
  Normal  Pulled     55s        kubelet, host  Container image &quot;registry.com/image:c1d98da0c17f9b1d4ca81713c138ee2e&quot; already present on machine
  Normal  Created    55s        kubelet, host  Created container build
  Normal  Started    54s        kubelet, host  Started container build
  Normal  Pulled     54s        kubelet, host  Container image &quot;gitlab/gitlab-runner-helper:x86_64-6214287e&quot; already present on machine
  Normal  Created    54s        kubelet, host  Created container helper
  Normal  Started    54s        kubelet, host  Started container helper

</code></pre>
<p>The provided information is not exactly detailed as to figure out exactly what is happening.</p>
<p><strong>Question:</strong></p>
<p>How can we gather more detailed metrics of what exactly and when exactly something happens in regards to get a Pod running in order to troubleshoot which step exactly needs how much time?</p>
<p>Special interest would be the metric of how long it takes to mount a volume.</p>

Dejan Jukic
<p>Check kubelet and kube scheduler logs because kube scheduler schedules the pod to a node and kubelet starts the pod on that node and reports the status as ready.</p>
<pre><code>journalctl -u kubelet # after logging into the kubernetes node

kubectl logs kube-scheduler -n kube-system
</code></pre>
<p>Describe the pod, deployment, replicaset to get more details</p>
<pre><code>kubectl describe pod podnanme -n namespacename
kubectl describe deploy deploymentnanme -n namespacename
kubectl describe rs replicasetnanme -n namespacename
</code></pre>
<p>Check events</p>
<pre><code>kubectl get events -n namespacename
</code></pre>
<p>Describe the nodes and check available resources and status which should be ready.</p>
<pre><code>kubectl describe node nodename
</code></pre>
