<p>When we run <code>kubectl apply -f</code>, we create a new pod in Kubernetes. But it takes about 5 seconds to arrive <code>Running</code> status even though the image has been already pulled in the node. Before that, the pod is in <code>containercreating</code> status. I Run <code>kubectl describe </code> to see the events and found that the scheduling is very fast but the gap between scheduled and imagepulling is about 3 seconds , and the container starting time is about 2 seconds. I wonder if I can reduce the time of containercreating time.  Thank you!</p>

<p>The target latency between Creation to Running is ~5 sec (if the image is pre-pulled). Your Pods' creation times are meeting both the scheduling time goal and the API latency goal. There was a <a href="https://github.com/kubernetes/kubernetes/issues/3954" rel="nofollow noreferrer">discussion</a> regarding that topic which resulted in the current SLA. And further <a href="https://github.com/kubernetes/enhancements/issues/1446" rel="nofollow noreferrer">Enhancement Proposals</a> (example) are rejected.</p>
<p>However you may want to review the <a href="https://kubernetes.io/docs/concepts/scheduling-eviction/scheduler-perf-tuning/" rel="nofollow noreferrer">Scheduler Performance Tuning</a> but bear in mind that it would be relevant for large Kubernetes clusters mainly.</p>
