If partition is set to 0 in a StatefulSet's updateStrategy, what does this imply about the update process?

If partition is set to 0 in a StatefulSet's updateStrategy, what does this imply about the update process?

• A. All pods will be updated
• B. No pods are updated until manual approval
• C. Only a subset of pods will be updated
• D. Updates will occur in random order

Answer: (A)

Partition determines where the update starts in a StatefulSet. In a RollingUpdate, updates are applied in ordinal order, and any pod with an index equal to or greater than the partition will be updated while those with a smaller index stay on the current version. When partition is zero, the update starts with the first pod and continues through all pods, so every pod gets updated. This is why setting partition to zero results in updating all pods in the StatefulSet. If you used a higher partition, the lower-indexed pods would be skipped while higher-indexed ones are updated.

Partition determines where the update starts in a StatefulSet. In a RollingUpdate, updates are applied in ordinal order, and any pod with an index equal to or greater than the partition will be updated while those with a smaller index stay on the current version. When partition is zero, the update starts with the first pod and continues through all pods, so every pod gets updated. This is why setting partition to zero results in updating all pods in the StatefulSet. If you used a higher partition, the lower-indexed pods would be skipped while higher-indexed ones are updated.