[BUG]starrocks pod got error after scale-in fe component

[tianyue86]

Describe the env
Kubernetes: v1.31.1-aliyun.1
KubeBlocks: 1.0.0-beta.21
kbcli: 1.0.0-beta.8

To Reproduce
Steps to reproduce the behavior:

1. Create starrocks cluster using yaml below
   srce.yaml.txt
2. scale-out/in be fe: succeed

 kbcli cluster list-ops strsce-ixtqee --status all  --namespace default
NAME                                    NAMESPACE   TYPE                CLUSTER         COMPONENT   STATUS    PROGRESS   CREATED-TIME                 
strsce-ixtqee-horizontalscaling-zjrtg   default     HorizontalScaling   strsce-ixtqee   be          Succeed   3/3        Jan 06,2025 17:54  
strsce-ixtqee-horizontalscaling-wpwhd   default     HorizontalScaling   strsce-ixtqee   be          Succeed   3/3        Jan 06,2025  
strsce-ixtqee-horizontalscaling-mfn6h   default     HorizontalScaling   strsce-ixtqee   fe          Succeed   3/3        Jan 06,2025 17:58 
strsce-ixtqee-horizontalscaling-569bg   default     HorizontalScaling   strsce-ixtqee   fe          Succeed   3/3        Jan 06,2025 18:02 

3. Check pod status

kbcli cluster scale-in strsce-ixtqee --auto-approve --force=true --components fe --replicas 3 --namespace default
===>pod got error after scale-in fe component

k get pod | grep strs
strsce-ixtqee-be-0               1/1     Running    0               56m
strsce-ixtqee-be-1               1/1     Running    0               56m
strsce-ixtqee-fe-0               0/1     Error      0               57m
strsce-ixtqee-fe-1               1/1     Running    0               57m

4. describe pod

k describe pod strsce-ixtqee-fe-0

Events:
  Type    Reason                  Age                 From                     Message
  ----    ------                  ----                ----                     -------
  Normal  Scheduled               57m                 default-scheduler        Successfully assigned default/strsce-ixtqee-fe-0 to cn-zhangjiakou.10.0.0.145
  Normal  SuccessfulAttachVolume  57m                 attachdetach-controller  AttachVolume.Attach succeeded for volume "d-8vbg6dqw5lh0gptd9f8u"
  Normal  AllocIPSucceed          57m                 terway-daemon            Alloc IP 10.0.0.2/24 took 33.341592ms
  Normal  Pulled                  7m6s (x2 over 57m)  kubelet                  Container image "apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/fe-ubuntu:3.3.0" already present on machine
  Normal  Created                 7m6s (x2 over 57m)  kubelet                  Created container fe
  Normal  Started                 7m6s (x2 over 57m)  kubelet                  Started container fe

5. logs

report-cluster-strsce-ixtqee-2025-01-06-18-22-14

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[shanshanying]

known issue. It is recommened to set FE with 3 replicas for HA.