<p>I have my Kubernetes cluster and I need to know how long it takes to create a pod? Is there any Kubernetes command show me that ?
Thanks in advance</p>

MOBT
<p>What you are asking for is not existing.</p>

<p>I think you should first understand the <a href="https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/" rel="nofollow noreferrer">Pod Overview</a>.</p>

<blockquote>
  <p>A  <em>Pod</em>  is the basic building block of Kubernetes–the smallest and simplest unit in the Kubernetes object model that you create or deploy. A Pod represents a running process on your cluster.</p>
  
  <p>A Pod encapsulates an application container (or, in some cases, multiple containers), storage resources, a unique network IP, and options that govern how the container(s) should run. A Pod represents a unit of deployment:  <em>a single instance of an application in Kubernetes</em>, which might consist of either a single container or a small number of containers that are tightly coupled and that share resources.</p>
</blockquote>

<p>While you are deploying a <code>POD</code> it's going through <code>phases</code></p>

<blockquote>
  <p><code>Pending</code>
  The Pod has been accepted by the Kubernetes system, but one or more of the Container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while.</p>
  
  <p><code>Running</code>
  The Pod has been bound to a node, and all of the Containers have been created. At least one Container is still running, or is in the process of starting or restarting.</p>
  
  <p><code>Succeeded</code>
  All Containers in the Pod have terminated in success, and will not be restarted.</p>
  
  <p><code>Failed</code>
  All Containers in the Pod have terminated, and at least one Container has terminated in failure. That is, the Container either exited with non-zero status or was terminated by the system.</p>
  
  <p><code>Unknown</code>
  For some reason the state of the Pod could not be obtained, typically due to an error in communicating with the 
  host of the Pod.</p>
</blockquote>

<p>As for <a href="https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions" rel="nofollow noreferrer">Pod Conditions</a> it have a <code>type</code> which can have following values:</p>

<blockquote>
  <ul>
  <li><code>PodScheduled</code>: the Pod has been scheduled to a node;</li>
  <li><code>Ready</code>: the Pod is able to serve requests and should be added to the load balancing pools of all matching Services;</li>
  <li><code>Initialized</code>: all  <a href="https://kubernetes.io/docs/concepts/workloads/pods/init-containers" rel="nofollow noreferrer">init containers</a>  have started successfully;</li>
  <li><code>Unschedulable</code>: the scheduler cannot schedule the Pod right now, for example due to lacking of resources or other constraints;</li>
  <li><code>ContainersReady</code>: all containers in the Pod are ready.</li>
  </ul>
</blockquote>

<p>Please refer to the documentation regarding <a href="https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/" rel="nofollow noreferrer">Pod Lifecycle</a> for more information.</p>

<p>When you are deploying your <code>POD</code>, you have to consider how many containers will be running in it.
The image will have to be downloaded, depending on the size it might take longer. Also default pull policy is <code>IfNotPresent</code>, which means that Kubernetes will skip the image pull if it already exists.
You can find more about <a href="https://kubernetes.io/docs/concepts/containers/images/#updating-images" rel="nofollow noreferrer">Updating Images</a> can be found <a href="https://kubernetes.io/docs/concepts/containers/images/" rel="nofollow noreferrer">here</a>.</p>

<p>You also need to consider how much resources your <code>Master</code> and <code>Node</code> has.</p>
