You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using a quite conservative k8s strategy, and now on 1.24, without alpha features. (No MaxUnavailable field.) Most of our workloads are native StatefulSet and we cannot change it.
Now we want to make its rollout quicker with 25% pods MaxUnavailable. I write a rollout like this:
The sts: podManagementPolicy is Parallel, updateStrategy is type: RollingUpdate
Now rollout works, but during its steps, it still rollout its pods one by one like native, not in batch. I want inner step, just remove all pods in this step. Is this supported? Or do I config something wrong?
Thanks.
The text was updated successfully, but these errors were encountered:
I'm afraid it is not supported, kruise rollout still relies on the referenced workload to manage the pod, and it make no sense to support the maxUnavailable of native statefulset below 1.24.
We're using a quite conservative k8s strategy, and now on 1.24, without alpha features. (No
MaxUnavailable
field.) Most of our workloads are native StatefulSet and we cannot change it.Now we want to make its rollout quicker with 25% pods MaxUnavailable. I write a rollout like this:
The sts:
podManagementPolicy
isParallel
,updateStrategy
istype: RollingUpdate
Now rollout works, but during its steps, it still rollout its pods one by one like native, not in batch. I want inner step, just remove all pods in this step. Is this supported? Or do I config something wrong?
Thanks.
The text was updated successfully, but these errors were encountered: