fix: member leave fails

Author: cjc7373

addons/tidb/scripts/pd_memberleave.sh

@@ -6,6 +6,13 @@ echo "$KB_LEAVE_MEMBER_POD_NAME"
 res=$(/pd-ctl member delete name "$KB_LEAVE_MEMBER_POD_NAME")
 echo "$res"
 not_found_pattern="Failed to delete member.*not found"
-if [[ $res != "Success!" && ! $res =~ $not_found_pattern ]]; then
+# this redirect_not_leader_pattern is a workaround when scaling in multiple pd instances,
+# pd cluster may fail to create a new leader until the deleted members' pod is stopped.
+# See: https://github.com/apecloud/apecloud/issues/13893#issuecomment-3574029284
+# In the future, when scale in is implemented in instanceset controller, we can have a better
+# solution that does memberLeave one by one. 
+redirect_not_leader_pattern="redirect to not leader"
+if [[ $res != "Success!" && ! $res =~ $not_found_pattern && ! $res =~ $redirect_not_leader_pattern ]]; then
     exit 1
 fi
+echo "member leave success"

addons/tidb/templates/cmpd-tidb.yaml

@@ -11,6 +11,7 @@ spec:
   description: tidb's SQL layer
   serviceKind: MySQL
   updateStrategy: BestEffortParallel
+  podManagementPolicy: Parallel
   vars:
     - name: CLUSTER_NAMESPACE
       valueFrom:

addons/tidb/templates/cmpd-tikv.yaml

@@ -10,6 +10,7 @@ spec:
   provider: kubeblocks
   description: a distributed transactional key-value database
   updateStrategy: BestEffortParallel
+  podManagementPolicy: Parallel
   vars:
     - name: CLUSTER_NAMESPACE
       valueFrom: