<p>I am trying to get the performance of the pod scheduling.</p>

<p>When kubectl describe pod performancetestpod. We will get something similar as shown below</p>

<pre><code>Type    Reason     Age   From                       Message
  ----    ------     ----  ----                       -------
  Normal  Scheduled  21s   default-scheduler          Successfully assigned default/performancetestpod to ip-172-31-22-111
  Normal  Pulled     20s   kubelet, ip-172-31-22-111  Container image "centos:7.6.1810" already present on machine
  Normal  Created    20s   kubelet, ip-172-31-22-111  Created container
  Normal  Started    20s   kubelet, ip-172-31-22-111  Started container
  Normal  Killing    10s   kubelet, ip-172-31-22-111  Killing container with id docker://performancetestpod:Need to kill Pod
</code></pre>

<p>1, Is there any way to get the age in milliseconds. </p>

<p>2, Is there any other way to get values in milliseconds for pod start, for eg: by using prometheus etc</p>

JibinNajeeb
<p>From my experience there is no way to get  milliseconds using kubectl in the way you do it.
Answering your 2nd question - take a closer look at <a href="https://github.com/kubernetes/kube-state-metrics" rel="nofollow noreferrer">kube-state-metrics</a>.
As per <a href="https://blog.freshtracks.io/a-deep-dive-into-kubernetes-metrics-part-6-kube-state-metrics-14f4e7c8710b" rel="nofollow noreferrer">A Deep Dive into Kubernetes Metrics</a> article:</p>

<p><strong>Object Creation Time</strong></p>

<p>Often is it helpful to know at what time objects in Kubernetes where created. Kube-state-metrics exposes a creation time for almost all the objects it tracks. The metric name follows the pattern <code>kube_&lt;OBJECT&gt;_created</code> and will include values for the name of the object and the namespace where it lives. The value is an epoch timestamp to the <strong>millisecond</strong>.</p>

<p>For example, the CronJob creation series is called <code>kube_cronjob_created</code>.</p>
