Describe the bug
The replicas field in KB v1.0.1 can work like sts partition and control which pods can be updated. But after v1.0.2，all pods are updated with replicas specified.
// RollingUpdate specifies how the rolling update should be applied. type RollingUpdate struct { // Indicates the number of instances that should be updated during a rolling update. // **_The remaining instances will remain untouched_**. This is helpful in defining how many instances // should participate in the update process. // Value can be an absolute number (ex: 5) or a percentage of desired instances (ex: 10%). // Absolute number is calculated from percentage by rounding up. // The default value is ComponentSpec.Replicas (i.e., update all instances). // // +optional Replicas *intstr.IntOrStringjson:"replicas,omitempty"
To Reproduce
Steps to reproduce the behavior:
- install kb v1.0.2
- install any clusters with instanceUpdateStrategy/rollingUpdate/replicas < total pod count
- all pods are updated
Expected behavior
only pods count by instanceUpdateStrategy/rollingUpdate/replicas are updated
Screenshots
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION kubeblocks kb-system 4 2026-06-22 14:01:09.674018508 +0800 CST deployed kubeblocks-1.0.2 1.0.2
Desktop (please complete the following information):
Describe the bug
The replicas field in KB v1.0.1 can work like sts partition and control which pods can be updated. But after v1.0.2，all pods are updated with replicas specified.
// RollingUpdate specifies how the rolling update should be applied. type RollingUpdate struct { // Indicates the number of instances that should be updated during a rolling update. // **_The remaining instances will remain untouched_**. This is helpful in defining how many instances // should participate in the update process. // Value can be an absolute number (ex: 5) or a percentage of desired instances (ex: 10%). // Absolute number is calculated from percentage by rounding up. // The default value is ComponentSpec.Replicas (i.e., update all instances). // // +optional Replicas *intstr.IntOrStringjson:"replicas,omitempty"To Reproduce
Steps to reproduce the behavior:
Expected behavior
only pods count by instanceUpdateStrategy/rollingUpdate/replicas are updated
Screenshots
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION kubeblocks kb-system 4 2026-06-22 14:01:09.674018508 +0800 CST deployed kubeblocks-1.0.2 1.0.2Desktop (please complete the following information):