<p>currently we scaled one of our statefulsets to have 11 replicas. Our current updateStrategy is</p>

<pre><code>updateStrategy:
  type: RollingUpdate
</code></pre>

<p>If we deploy the statefulset from scratch, Kubernetes starts them one after another. To start one replica it needs around 5 Minutes. So in total we wait 55 Minutes just to fill up the capacity.</p>

<p>Is there a way to fill up the capacity at once when starting from scratch? So that all 11 replicas will start simultaneously?</p>

<p>Upgrades on the already existing statefulset should be handled via RollingUpdate due to failure safety.</p>

<p>Best wishes,
Stephan</p>

<p>we found the answer hiding deep in the documentation:</p>

<p><a href="https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#parallel-pod-management" rel="noreferrer">https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#parallel-pod-management</a></p>

<p><a href="https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#pod-management-policies" rel="noreferrer">https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#pod-management-policies</a></p>

<blockquote>
  <p><strong>Pod Management Policies</strong></p>
  
  <p>In Kubernetes 1.7 and later, StatefulSet allows you to relax its ordering guarantees while preserving its uniqueness and identity guarantees via its .spec.podManagementPolicy field.</p>
  
  <p><strong>OrderedReady Pod Management</strong></p>
  
  <p>OrderedReady pod management is the default for StatefulSets. It implements the behavior described above.</p>
  
  <p><strong>Parallel Pod Management</strong></p>
  
  <p>Parallel pod management tells the StatefulSet controller to launch or terminate all Pods in parallel, and to not wait for Pods to become Running and Ready or completely terminated prior to launching or terminating another Pod. This option only affects the behavior for scaling operations. Updates are not affected.</p>
</blockquote>
