<p>I start a kubernetes replication controller. When the corresponding container in the single pod in this replication controller has a <code>gcePersistentDisk</code> specified the pods will start very slow. After 5 minutes the pod is still in the <code>Pending</code> state.</p>

<p><code>kubectl get po</code> will tell me:</p>

<pre><code>NAME          READY     STATUS    RESTARTS   AGE
app-1-a4ni7   0/1       Pending   0          5m
</code></pre>

<p>Without the <code>gcePersistentDisk</code> the pod is <code>Running</code> in max 30 seconds.</p>

<p>(I am using a 10 GB Google Cloud Storage disk and I know that these disks have <a href="https://stackoverflow.com/q/23683271/454103">lower performance</a> for lower capacities, but I am not sure this is the issue.)</p>

<p>What could be the cause of this?</p>

<p>We've seen the GCE PD attach calls take upwards of 10 minutes to complete, so this is more or less expected. For example see <a href="https://github.com/kubernetes/kubernetes/issues/15382#issuecomment-153268655">https://github.com/kubernetes/kubernetes/issues/15382#issuecomment-153268655</a>, where PD tests were timing out before GCE PD attach/detach calls could complete. We're working with the GCE team to improve performance and reduce latency.</p>

<p>If the pod never gets out of pending state, then you might've hit a bug. In that case, grab your kubelet log and open an issue at <a href="https://github.com/kubernetes/kubernetes/">https://github.com/kubernetes/kubernetes/</a></p>
