source commons files source engines files source kubeblocks files kbcli is detected: /usr/local/bin/kbcli Kubernetes Env: v1.30.4-vke.4 check snapshot controller check snapshot controller done vke kb-default-sc found vke default-vsc found POD_RESOURCES: No resources found found default storage class: ebs-ssd KubeBlocks version is:1.0.0 skip upgrade KubeBlocks current KubeBlocks version: 1.0.0 check component definition No resources found KUBEBLOCKS NAMESPACE:kb-system get kubeblocks namespace done annotate polardbx cmpd apps.kubeblocks.io/skip-immutable-check=true No resources found get helm repo list success found helm repo kbcli-test-addons `helm repo update kbcli-test-addons ` Hang tight while we grab the latest from your chart repositories... ...Successfully got an update from the "kbcli-test-addons" chart repository Update Complete. ⎈Happy Helming!⎈ KUBEBLOCKS NAMESPACE:kb-system get kubeblocks namespace done current KubeBlocks version: 1.0.0 `helm upgrade --install --namespace kb-system kb-addon-polardbx kbcli-test-addons/polardbx --version 1.0.0-alpha.0 --set image.registry=apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com --set images.registry=apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com ` Release "kb-addon-polardbx" does not exist. Installing it now. NAME: kb-addon-polardbx LAST DEPLOYED: Wed May 28 12:46:27 2025 NAMESPACE: kb-system STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: Thanks for installing PolarDB-X using KubeBlocks! 1. Run the following command to create your first PolarDB-X cluster: ``` kbcli cluster create pxc --cluster-definition polardbx ``` 2. Port-forward service to localhost and connect to PolarDB-X cluster: ``` kubectl port-forward svc/pxc-cn 3306:3306 mysql -h127.0.0.1 -upolardbx_root ``` Release Information: Commit ID: "7cd69f1c1577fed5e7f6a17442c8bf7aa016edec" Commit Time: "2025-05-14 10:45:11 +0800" Release Branch: "v1.0.0" Release Time: "2025-05-28 10:53:50 +0800" Enterprise: "false" set component version set component version:polardbx-cdc set service versions:2.3.0 set service versions sorted:2.3.0 check component definition polardbx status done set component name:gms found component version set polardbx component definition set polardbx component definition polardbx-cn-1.0.0-alpha.0 set replicas first:3,2.3.0 set replicas third:3,2.3.0 set replicas fourth:3,2.3.0 set minimum cmpv service version set minimum cmpv service version replicas:3,2.3.0 REPORT_COUNT:1 CLUSTER_TOPOLOGY: Error from server (NotFound): clusterdefinitions.apps.kubeblocks.io "polardbx" not found Not found topology in cluster definition polardbx set polardbx component definition set polardbx component definition polardbx-dn-1.0.0-alpha.0 LIMIT_CPU:0.5 LIMIT_MEMORY:1 storage size: 20 No resources found in default namespace. termination_policy:DoNotTerminate create 3 replica DoNotTerminate polardbx cluster check component definition set component definition by component version check cmpd by labels check cmpd by compDefs set component definition: polardbx-cdc-1.0.0-alpha.0 by component version:polardbx-cdc apiVersion: apps.kubeblocks.io/v1 kind: Cluster metadata: name: px-sdv namespace: default spec: terminationPolicy: DoNotTerminate componentSpecs: - name: gms componentDef: polardbx-gms replicas: 3 resources: requests: cpu: 500m memory: 1Gi limits: cpu: 500m memory: 1Gi volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: dn componentDef: polardbx-dn replicas: 3 resources: requests: cpu: 500m memory: 1Gi limits: cpu: 500m memory: 1Gi volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: cn componentDef: polardbx-cn replicas: 1 resources: requests: cpu: 500m memory: 1Gi limits: cpu: 500m memory: 1Gi - name: cdc componentDef: polardbx-cdc replicas: 1 resources: requests: cpu: 500m memory: 1Gi limits: cpu: 500m memory: 1Gi `kubectl apply -f test_create_px-sdv.yaml` cluster.apps.kubeblocks.io/px-sdv created apply test_create_px-sdv.yaml Success `rm -rf test_create_px-sdv.yaml` check cluster status `kbcli cluster list px-sdv --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS px-sdv default DoNotTerminate Creating May 28,2025 12:46 UTC+0800 cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating `kubectl get pods -l app.kubernetes.io/instance=px-sdv -n default | (grep 'px-sdv-cn' || true)` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. pod "px-sdv-cn-0" force deleted cluster_status:Abnormal cluster_status:Abnormal cluster_status:Abnormal cluster_status:Abnormal cluster_status:Updating cluster_status:Abnormal cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances px-sdv --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME px-sdv-cdc-0 default px-sdv cdc Running cn-guangzhou-b 500m / 500m 1Gi / 1Gi 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 px-sdv-cn-0 default px-sdv cn Running cn-guangzhou-b 500m / 500m 1Gi / 1Gi 192.168.0.42/192.168.0.42 May 28,2025 12:56 UTC+0800 px-sdv-dn-0 default px-sdv dn Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 px-sdv-dn-1 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:47 UTC+0800 px-sdv-dn-2 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:52 UTC+0800 px-sdv-gms-0 default px-sdv gms Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 px-sdv-gms-1 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:47 UTC+0800 px-sdv-gms-2 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:48 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=px-sdv` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.username}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.password}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.port}"` DB_USERNAME:polardbx_root;DB_PASSWORD:74FrzWqyuc4njoR1;DB_PORT:;DB_DATABASE: check cluster connect `echo ' echo "select 1;" | mysql -hpx-sdv-dn.default.svc.cluster.local -P3306 -upolardbx_root -p"74FrzWqyuc4njoR1"' | kubectl exec -it px-sdv-dn-0 --namespace default -- bash ` check cluster connect done `kubectl get secrets -l app.kubernetes.io/instance=px-sdv` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.username}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.password}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.port}"` DB_USERNAME:polardbx_root;DB_PASSWORD:74FrzWqyuc4njoR1;DB_PORT:;DB_DATABASE: check pod px-sdv-gms-0 container_name engine exist password 74FrzWqyuc4njoR1 check pod px-sdv-gms-0 container_name exporter exist password 74FrzWqyuc4njoR1 check pod px-sdv-gms-0 container_name kbagent exist password 74FrzWqyuc4njoR1 No container logs contain secret password. describe cluster `kbcli cluster describe px-sdv --namespace default ` Name: px-sdv Created Time: May 28,2025 12:46 UTC+0800 NAMESPACE CLUSTER-DEFINITION TOPOLOGY STATUS TERMINATION-POLICY default Running DoNotTerminate Endpoints: COMPONENT INTERNAL EXTERNAL gms px-sdv-gms.default.svc.cluster.local:3306 px-sdv-gms.default.svc.cluster.local:9104 dn px-sdv-dn.default.svc.cluster.local:3306 cn px-sdv-cn.default.svc.cluster.local:3306 px-sdv-cn.default.svc.cluster.local:9104 cdc px-sdv-cdc.default.svc.cluster.local:3306 px-sdv-cdc.default.svc.cluster.local:9104 Topology: COMPONENT SERVICE-VERSION INSTANCE ROLE STATUS AZ NODE CREATED-TIME cdc 2.3.0 px-sdv-cdc-0 Running cn-guangzhou-b 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 cn 2.3.0 px-sdv-cn-0 Running cn-guangzhou-b 192.168.0.42/192.168.0.42 May 28,2025 12:56 UTC+0800 dn 2.3.0 px-sdv-dn-0 leader Running cn-guangzhou-b 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 dn 2.3.0 px-sdv-dn-1 follower Running cn-guangzhou-b 192.168.0.42/192.168.0.42 May 28,2025 12:47 UTC+0800 dn 2.3.0 px-sdv-dn-2 follower Running cn-guangzhou-b 192.168.0.42/192.168.0.42 May 28,2025 12:52 UTC+0800 gms 2.3.0 px-sdv-gms-0 leader Running cn-guangzhou-b 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 gms 2.3.0 px-sdv-gms-1 follower Running cn-guangzhou-b 192.168.0.18/192.168.0.18 May 28,2025 12:47 UTC+0800 gms 2.3.0 px-sdv-gms-2 follower Running cn-guangzhou-b 192.168.0.42/192.168.0.42 May 28,2025 12:48 UTC+0800 Resources Allocation: COMPONENT INSTANCE-TEMPLATE CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS gms 500m / 500m 1Gi / 1Gi data:20Gi ebs-ssd dn 500m / 500m 1Gi / 1Gi data:20Gi ebs-ssd cn 500m / 500m 1Gi / 1Gi cdc 500m / 500m 1Gi / 1Gi Images: COMPONENT COMPONENT-DEFINITION IMAGE gms polardbx-gms-1.0.0-alpha.0 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/polardbx-engine-2.0:80-8.0.18-20231101115000 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/mysqld-exporter:v0.14.0 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/mysql-client:latest dn polardbx-dn-1.0.0-alpha.0 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/polardbx-engine-2.0:80-8.0.18-20231101115000 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/mysqld-exporter:v0.14.0 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/mysql-client:latest cn polardbx-cn-1.0.0-alpha.0 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/polardbx-sql:5.4.18-20231101115000 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/polardbx-exporter:v1.5.0 cdc polardbx-cdc-1.0.0-alpha.0 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/polardbx-cdc:5.4.18-20231101115000 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/polardbx-exporter:v1.5.0 Show cluster events: kbcli cluster list-events -n default px-sdv `kbcli cluster label px-sdv app.kubernetes.io/instance- --namespace default ` label "app.kubernetes.io/instance" not found. `kbcli cluster label px-sdv app.kubernetes.io/instance=px-sdv --namespace default ` `kbcli cluster label px-sdv --list --namespace default ` NAME NAMESPACE LABELS px-sdv default app.kubernetes.io/instance=px-sdv label cluster app.kubernetes.io/instance=px-sdv Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=px-sdv --namespace default ` `kbcli cluster label px-sdv --list --namespace default ` NAME NAMESPACE LABELS px-sdv default app.kubernetes.io/instance=px-sdv case.name=kbcli.test1 label cluster case.name=kbcli.test1 Success `kbcli cluster label px-sdv case.name=kbcli.test2 --overwrite --namespace default ` `kbcli cluster label px-sdv --list --namespace default ` NAME NAMESPACE LABELS px-sdv default app.kubernetes.io/instance=px-sdv case.name=kbcli.test2 label cluster case.name=kbcli.test2 Success `kbcli cluster label px-sdv case.name- --namespace default ` `kbcli cluster label px-sdv --list --namespace default ` NAME NAMESPACE LABELS px-sdv default app.kubernetes.io/instance=px-sdv delete cluster label case.name Success cluster does not need to check monitor currently check cluster status `kbcli cluster list px-sdv --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS px-sdv default DoNotTerminate Running May 28,2025 12:46 UTC+0800 app.kubernetes.io/instance=px-sdv check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances px-sdv --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME px-sdv-cdc-0 default px-sdv cdc Running cn-guangzhou-b 500m / 500m 1Gi / 1Gi 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 px-sdv-cn-0 default px-sdv cn Running cn-guangzhou-b 500m / 500m 1Gi / 1Gi 192.168.0.42/192.168.0.42 May 28,2025 12:56 UTC+0800 px-sdv-dn-0 default px-sdv dn Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 px-sdv-dn-1 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:47 UTC+0800 px-sdv-dn-2 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:52 UTC+0800 px-sdv-gms-0 default px-sdv gms Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 px-sdv-gms-1 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:47 UTC+0800 px-sdv-gms-2 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:48 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=px-sdv` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.username}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.password}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.port}"` DB_USERNAME:polardbx_root;DB_PASSWORD:74FrzWqyuc4njoR1;DB_PORT:;DB_DATABASE: check cluster connect `echo ' echo "select 1;" | mysql -hpx-sdv-dn.default.svc.cluster.local -P3306 -upolardbx_root -p"74FrzWqyuc4njoR1"' | kubectl exec -it px-sdv-dn-0 --namespace default -- bash ` check cluster connect done check component cn exists `kubectl get components -l app.kubernetes.io/instance=px-sdv,apps.kubeblocks.io/component-name=cn --namespace default | (grep "cn" || true )` check component cdc exists `kubectl get components -l app.kubernetes.io/instance=px-sdv,apps.kubeblocks.io/component-name=cdc --namespace default | (grep "cdc" || true )` check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale px-sdv --auto-approve --force=true --components cn,cdc --cpu 600m --memory 1.1Gi --namespace default ` OpsRequest px-sdv-verticalscaling-bc468 created successfully, you can view the progress: kbcli cluster describe-ops px-sdv-verticalscaling-bc468 -n default check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-verticalscaling-bc468 default VerticalScaling px-sdv cn,cdc Running 0/2 May 28,2025 13:03 UTC+0800 check cluster status `kbcli cluster list px-sdv --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS px-sdv default DoNotTerminate Updating May 28,2025 12:46 UTC+0800 app.kubernetes.io/instance=px-sdv cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances px-sdv --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME px-sdv-cdc-0 default px-sdv cdc Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:03 UTC+0800 px-sdv-cn-0 default px-sdv cn Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:03 UTC+0800 px-sdv-dn-0 default px-sdv dn Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 px-sdv-dn-1 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:47 UTC+0800 px-sdv-dn-2 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:52 UTC+0800 px-sdv-gms-0 default px-sdv gms Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 px-sdv-gms-1 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:47 UTC+0800 px-sdv-gms-2 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:48 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=px-sdv` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.username}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.password}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.port}"` DB_USERNAME:polardbx_root;DB_PASSWORD:74FrzWqyuc4njoR1;DB_PORT:;DB_DATABASE: check cluster connect `echo ' echo "select 1;" | mysql -hpx-sdv-dn.default.svc.cluster.local -P3306 -upolardbx_root -p"74FrzWqyuc4njoR1"' | kubectl exec -it px-sdv-dn-0 --namespace default -- bash ` check cluster connect done check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-verticalscaling-bc468 default VerticalScaling px-sdv cn,cdc Succeed 2/2 May 28,2025 13:03 UTC+0800 check ops status done ops_status:px-sdv-verticalscaling-bc468 default VerticalScaling px-sdv cn,cdc Succeed 2/2 May 28,2025 13:03 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations px-sdv-verticalscaling-bc468 --namespace default ` opsrequest.operations.kubeblocks.io/px-sdv-verticalscaling-bc468 patched `kbcli cluster delete-ops --name px-sdv-verticalscaling-bc468 --force --auto-approve --namespace default ` OpsRequest px-sdv-verticalscaling-bc468 deleted check component cn exists `kubectl get components -l app.kubernetes.io/instance=px-sdv,apps.kubeblocks.io/component-name=cn --namespace default | (grep "cn" || true )` check component cdc exists `kubectl get components -l app.kubernetes.io/instance=px-sdv,apps.kubeblocks.io/component-name=cdc --namespace default | (grep "cdc" || true )` cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart px-sdv --auto-approve --force=true --components cn,cdc --namespace default ` OpsRequest px-sdv-restart-lnh2m created successfully, you can view the progress: kbcli cluster describe-ops px-sdv-restart-lnh2m -n default check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-restart-lnh2m default Restart px-sdv cn,cdc Running 0/2 May 28,2025 13:06 UTC+0800 check cluster status `kbcli cluster list px-sdv --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS px-sdv default DoNotTerminate Updating May 28,2025 12:46 UTC+0800 app.kubernetes.io/instance=px-sdv cluster_status:Updating cluster_status:Abnormal cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances px-sdv --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME px-sdv-cdc-0 default px-sdv cdc Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:07 UTC+0800 px-sdv-cn-0 default px-sdv cn Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:07 UTC+0800 px-sdv-dn-0 default px-sdv dn Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 px-sdv-dn-1 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:47 UTC+0800 px-sdv-dn-2 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:52 UTC+0800 px-sdv-gms-0 default px-sdv gms Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:46 UTC+0800 px-sdv-gms-1 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 12:47 UTC+0800 px-sdv-gms-2 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:48 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=px-sdv` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.username}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.password}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.port}"` DB_USERNAME:polardbx_root;DB_PASSWORD:74FrzWqyuc4njoR1;DB_PORT:;DB_DATABASE: check cluster connect `echo ' echo "select 1;" | mysql -hpx-sdv-dn.default.svc.cluster.local -P3306 -upolardbx_root -p"74FrzWqyuc4njoR1"' | kubectl exec -it px-sdv-dn-0 --namespace default -- bash ` check cluster connect done check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-restart-lnh2m default Restart px-sdv cn,cdc Succeed 2/2 May 28,2025 13:06 UTC+0800 check ops status done ops_status:px-sdv-restart-lnh2m default Restart px-sdv cn,cdc Succeed 2/2 May 28,2025 13:06 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations px-sdv-restart-lnh2m --namespace default ` opsrequest.operations.kubeblocks.io/px-sdv-restart-lnh2m patched `kbcli cluster delete-ops --name px-sdv-restart-lnh2m --force --auto-approve --namespace default ` OpsRequest px-sdv-restart-lnh2m deleted cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop px-sdv --auto-approve --force=true --namespace default ` OpsRequest px-sdv-stop-tm6gv created successfully, you can view the progress: kbcli cluster describe-ops px-sdv-stop-tm6gv -n default check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-stop-tm6gv default Stop px-sdv cdc,cn,dn,gms Running 0/8 May 28,2025 13:09 UTC+0800 check cluster status `kbcli cluster list px-sdv --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS px-sdv default DoNotTerminate Stopping May 28,2025 12:46 UTC+0800 app.kubernetes.io/instance=px-sdv cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping check cluster status done cluster_status:Stopped check pod status `kbcli cluster list-instances px-sdv --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME check pod status done check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-stop-tm6gv default Stop px-sdv cdc,cn,dn,gms Succeed 8/8 May 28,2025 13:09 UTC+0800 check ops status done ops_status:px-sdv-stop-tm6gv default Stop px-sdv cdc,cn,dn,gms Succeed 8/8 May 28,2025 13:09 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations px-sdv-stop-tm6gv --namespace default ` opsrequest.operations.kubeblocks.io/px-sdv-stop-tm6gv patched `kbcli cluster delete-ops --name px-sdv-stop-tm6gv --force --auto-approve --namespace default ` OpsRequest px-sdv-stop-tm6gv deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start px-sdv --force=true --namespace default ` OpsRequest px-sdv-start-4qvpp created successfully, you can view the progress: kbcli cluster describe-ops px-sdv-start-4qvpp -n default check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-start-4qvpp default Start px-sdv cdc,cn,dn,gms Running 0/8 May 28,2025 13:11 UTC+0800 check cluster status `kbcli cluster list px-sdv --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS px-sdv default DoNotTerminate Updating May 28,2025 12:46 UTC+0800 app.kubernetes.io/instance=px-sdv cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances px-sdv --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME px-sdv-cdc-0 default px-sdv cdc Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-cn-0 default px-sdv cn Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-dn-0 default px-sdv dn Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-dn-1 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 13:12 UTC+0800 px-sdv-dn-2 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 13:13 UTC+0800 px-sdv-gms-0 default px-sdv gms Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-gms-1 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 13:12 UTC+0800 px-sdv-gms-2 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:20Gi 192.168.0.18/192.168.0.18 May 28,2025 13:12 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=px-sdv` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.username}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.password}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.port}"` DB_USERNAME:polardbx_root;DB_PASSWORD:74FrzWqyuc4njoR1;DB_PORT:;DB_DATABASE: check cluster connect `echo ' echo "select 1;" | mysql -hpx-sdv-dn.default.svc.cluster.local -P3306 -upolardbx_root -p"74FrzWqyuc4njoR1"' | kubectl exec -it px-sdv-dn-0 --namespace default -- bash ` check cluster connect done check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-start-4qvpp default Start px-sdv cdc,cn,dn,gms Succeed 8/8 May 28,2025 13:11 UTC+0800 check ops status done ops_status:px-sdv-start-4qvpp default Start px-sdv cdc,cn,dn,gms Succeed 8/8 May 28,2025 13:11 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations px-sdv-start-4qvpp --namespace default ` opsrequest.operations.kubeblocks.io/px-sdv-start-4qvpp patched `kbcli cluster delete-ops --name px-sdv-start-4qvpp --force --auto-approve --namespace default ` OpsRequest px-sdv-start-4qvpp deleted check component gms exists `kubectl get components -l app.kubernetes.io/instance=px-sdv,apps.kubeblocks.io/component-name=gms --namespace default | (grep "gms" || true )` check component dn exists `kubectl get components -l app.kubernetes.io/instance=px-sdv,apps.kubeblocks.io/component-name=dn --namespace default | (grep "dn" || true )` `kubectl get pvc -l app.kubernetes.io/instance=px-sdv,apps.kubeblocks.io/component-name=gms,dn,apps.kubeblocks.io/vct-name=data --namespace default ` No resources found in default namespace. px-sdv gms,dn data pvc is empty cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in px-sdv namespace. `kbcli cluster volume-expand px-sdv --auto-approve --force=true --components gms,dn --volume-claim-templates data --storage 24Gi --namespace default ` OpsRequest px-sdv-volumeexpansion-pfwcp created successfully, you can view the progress: kbcli cluster describe-ops px-sdv-volumeexpansion-pfwcp -n default check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-volumeexpansion-pfwcp default VolumeExpansion px-sdv gms,dn Running 0/6 May 28,2025 13:16 UTC+0800 check cluster status `kbcli cluster list px-sdv --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS px-sdv default DoNotTerminate Updating May 28,2025 12:46 UTC+0800 app.kubernetes.io/instance=px-sdv cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances px-sdv --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME px-sdv-cdc-0 default px-sdv cdc Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-cn-0 default px-sdv cn Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-dn-0 default px-sdv dn Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-dn-1 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:12 UTC+0800 px-sdv-dn-2 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:13 UTC+0800 px-sdv-gms-0 default px-sdv gms Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-gms-1 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:12 UTC+0800 px-sdv-gms-2 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.18/192.168.0.18 May 28,2025 13:12 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=px-sdv` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.username}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.password}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.port}"` DB_USERNAME:polardbx_root;DB_PASSWORD:74FrzWqyuc4njoR1;DB_PORT:;DB_DATABASE: check cluster connect `echo ' echo "select 1;" | mysql -hpx-sdv-dn.default.svc.cluster.local -P3306 -upolardbx_root -p"74FrzWqyuc4njoR1"' | kubectl exec -it px-sdv-dn-0 --namespace default -- bash ` check cluster connect done No resources found in px-sdv namespace. check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-volumeexpansion-pfwcp default VolumeExpansion px-sdv gms,dn Succeed 6/6 May 28,2025 13:16 UTC+0800 check ops status done ops_status:px-sdv-volumeexpansion-pfwcp default VolumeExpansion px-sdv gms,dn Succeed 6/6 May 28,2025 13:16 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations px-sdv-volumeexpansion-pfwcp --namespace default ` opsrequest.operations.kubeblocks.io/px-sdv-volumeexpansion-pfwcp patched `kbcli cluster delete-ops --name px-sdv-volumeexpansion-pfwcp --force --auto-approve --namespace default ` OpsRequest px-sdv-volumeexpansion-pfwcp deleted check component cn exists `kubectl get components -l app.kubernetes.io/instance=px-sdv,apps.kubeblocks.io/component-name=cn --namespace default | (grep "cn" || true )` check component cdc exists `kubectl get components -l app.kubernetes.io/instance=px-sdv,apps.kubeblocks.io/component-name=cdc --namespace default | (grep "cdc" || true )` cluster cn,cdc scale-out check cluster status before ops check cluster status done cluster_status:Running No resources found in px-sdv namespace. `kbcli cluster scale-out px-sdv --auto-approve --force=true --components cn,cdc --replicas 1 --namespace default ` OpsRequest px-sdv-horizontalscaling-98fj8 created successfully, you can view the progress: kbcli cluster describe-ops px-sdv-horizontalscaling-98fj8 -n default check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-horizontalscaling-98fj8 default HorizontalScaling px-sdv cn,cdc Running 0/2 May 28,2025 13:17 UTC+0800 check cluster status `kbcli cluster list px-sdv --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS px-sdv default DoNotTerminate Updating May 28,2025 12:46 UTC+0800 app.kubernetes.io/instance=px-sdv cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances px-sdv --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME px-sdv-cdc-0 default px-sdv cdc Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-cdc-1 default px-sdv cdc Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:17 UTC+0800 px-sdv-cn-0 default px-sdv cn Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-cn-1 default px-sdv cn Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:17 UTC+0800 px-sdv-dn-0 default px-sdv dn Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-dn-1 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:12 UTC+0800 px-sdv-dn-2 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:13 UTC+0800 px-sdv-gms-0 default px-sdv gms Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-gms-1 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:12 UTC+0800 px-sdv-gms-2 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.18/192.168.0.18 May 28,2025 13:12 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=px-sdv` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.username}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.password}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.port}"` DB_USERNAME:polardbx_root;DB_PASSWORD:74FrzWqyuc4njoR1;DB_PORT:;DB_DATABASE: check cluster connect `echo ' echo "select 1;" | mysql -hpx-sdv-dn.default.svc.cluster.local -P3306 -upolardbx_root -p"74FrzWqyuc4njoR1"' | kubectl exec -it px-sdv-dn-0 --namespace default -- bash ` check cluster connect done No resources found in px-sdv namespace. check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-horizontalscaling-98fj8 default HorizontalScaling px-sdv cn,cdc Succeed 2/2 May 28,2025 13:17 UTC+0800 check ops status done ops_status:px-sdv-horizontalscaling-98fj8 default HorizontalScaling px-sdv cn,cdc Succeed 2/2 May 28,2025 13:17 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations px-sdv-horizontalscaling-98fj8 --namespace default ` opsrequest.operations.kubeblocks.io/px-sdv-horizontalscaling-98fj8 patched `kbcli cluster delete-ops --name px-sdv-horizontalscaling-98fj8 --force --auto-approve --namespace default ` OpsRequest px-sdv-horizontalscaling-98fj8 deleted check component cn exists `kubectl get components -l app.kubernetes.io/instance=px-sdv,apps.kubeblocks.io/component-name=cn --namespace default | (grep "cn" || true )` check component cdc exists `kubectl get components -l app.kubernetes.io/instance=px-sdv,apps.kubeblocks.io/component-name=cdc --namespace default | (grep "cdc" || true )` cluster cn,cdc scale-in check cluster status before ops check cluster status done cluster_status:Running No resources found in px-sdv namespace. `kbcli cluster scale-in px-sdv --auto-approve --force=true --components cn,cdc --replicas 1 --namespace default ` OpsRequest px-sdv-horizontalscaling-5fhdv created successfully, you can view the progress: kbcli cluster describe-ops px-sdv-horizontalscaling-5fhdv -n default check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-horizontalscaling-5fhdv default HorizontalScaling px-sdv cn,cdc Running 0/2 May 28,2025 13:17 UTC+0800 check cluster status `kbcli cluster list px-sdv --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS px-sdv default DoNotTerminate Running May 28,2025 12:46 UTC+0800 app.kubernetes.io/instance=px-sdv check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances px-sdv --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME px-sdv-cdc-0 default px-sdv cdc Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-cn-0 default px-sdv cn Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-dn-0 default px-sdv dn Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-dn-1 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:12 UTC+0800 px-sdv-dn-2 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:13 UTC+0800 px-sdv-gms-0 default px-sdv gms Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-gms-1 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:12 UTC+0800 px-sdv-gms-2 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.18/192.168.0.18 May 28,2025 13:12 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=px-sdv` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.username}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.password}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.port}"` DB_USERNAME:polardbx_root;DB_PASSWORD:74FrzWqyuc4njoR1;DB_PORT:;DB_DATABASE: check cluster connect `echo ' echo "select 1;" | mysql -hpx-sdv-dn.default.svc.cluster.local -P3306 -upolardbx_root -p"74FrzWqyuc4njoR1"' | kubectl exec -it px-sdv-dn-0 --namespace default -- bash ` check cluster connect done No resources found in px-sdv namespace. check ops status `kbcli cluster list-ops px-sdv --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME px-sdv-horizontalscaling-5fhdv default HorizontalScaling px-sdv cn,cdc Succeed 2/2 May 28,2025 13:17 UTC+0800 check ops status done ops_status:px-sdv-horizontalscaling-5fhdv default HorizontalScaling px-sdv cn,cdc Succeed 2/2 May 28,2025 13:17 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations px-sdv-horizontalscaling-5fhdv --namespace default ` opsrequest.operations.kubeblocks.io/px-sdv-horizontalscaling-5fhdv patched `kbcli cluster delete-ops --name px-sdv-horizontalscaling-5fhdv --force --auto-approve --namespace default ` OpsRequest px-sdv-horizontalscaling-5fhdv deleted cluster update terminationPolicy WipeOut `kbcli cluster update px-sdv --termination-policy=WipeOut --namespace default ` cluster.apps.kubeblocks.io/px-sdv updated check cluster status `kbcli cluster list px-sdv --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS px-sdv default WipeOut Running May 28,2025 12:46 UTC+0800 app.kubernetes.io/instance=px-sdv check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances px-sdv --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME px-sdv-cdc-0 default px-sdv cdc Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-cn-0 default px-sdv cn Running cn-guangzhou-b 600m / 600m 1181116006400m / 1181116006400m 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-dn-0 default px-sdv dn Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-dn-1 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:12 UTC+0800 px-sdv-dn-2 default px-sdv dn Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:13 UTC+0800 px-sdv-gms-0 default px-sdv gms Running leader cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:11 UTC+0800 px-sdv-gms-1 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.42/192.168.0.42 May 28,2025 13:12 UTC+0800 px-sdv-gms-2 default px-sdv gms Running follower cn-guangzhou-b 500m / 500m 1Gi / 1Gi data:24Gi 192.168.0.18/192.168.0.18 May 28,2025 13:12 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=px-sdv` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.username}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.password}"` `kubectl get secrets px-sdv-gms-account-polardbx-root -o jsonpath="{.data.port}"` DB_USERNAME:polardbx_root;DB_PASSWORD:74FrzWqyuc4njoR1;DB_PORT:;DB_DATABASE: check cluster connect `echo ' echo "select 1;" | mysql -hpx-sdv-dn.default.svc.cluster.local -P3306 -upolardbx_root -p"74FrzWqyuc4njoR1"' | kubectl exec -it px-sdv-dn-0 --namespace default -- bash ` check cluster connect done cluster list-logs `kbcli cluster list-logs px-sdv --namespace default ` No log files found. cluster logs `kbcli cluster logs px-sdv --tail 30 --namespace default ` Defaulted container "engine" out of: engine, exporter, kbagent, tools-updater (init), init-kbagent (init), kbagent-worker (init) 2025-05-28 05:12:05,637 - GalaxyEngine - INFO - finish wait for enable 2025-05-28 05:12:05,645 - AuditController - INFO - Start Audit Controller Process: ['/tools/xstore/current/venv/bin/python3', '/tools/xstore/v1.5.0-1700478258.106533/audit_controller.py'] INFO:root:Bootstrapping engine galaxy ... 2025-05-28 05:12:05,653 - GalaxyEngine - INFO - log_data_separtion False, source_path /data/mysql/log, destination_path /data/mysql/log 2025-05-28 05:12:05,653 - GalaxyEngine - INFO - log_data_separtion False, source_path /data/mysql/log, destination_path /data/mysql/log 2025-05-28 05:12:05,653 - GalaxyEngine - INFO - It not necessary to mv data because the source_path equals the destination_path 2025-05-28 05:12:05,653 - GalaxyEngine - INFO - It not necessary to mv data because the source_path equals the destination_path 2025-05-28 05:12:05,654 - GalaxyEngine - INFO - starting process... 2025-05-28 05:12:05,654 - GalaxyEngine - INFO - starting process... 2025-05-28 05:12:05,654 - GalaxyEngine - INFO - () start command: /opt/galaxy_engine/bin/mysqld_safe --defaults-file=/data/mysql/conf/my.cnf --loose-pod-name=px-sdv-gms-0 2025-05-28 05:12:05,654 - GalaxyEngine - INFO - () start command: /opt/galaxy_engine/bin/mysqld_safe --defaults-file=/data/mysql/conf/my.cnf --loose-pod-name=px-sdv-gms-0 /tools/xstore/current/venv/lib64/python3.6/site-packages/pymysql/_auth.py:8: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography. The next release of cryptography will remove support for Python 3.6. from cryptography.hazmat.backends import default_backend 2025-05-28 05:12:06,097 - AuditController - INFO - Creating mysql connection pool... 2025-05-28 05:12:06,103 - AuditController - ERROR - Creating mysql connection pool failed: 2003: Can't connect to MySQL server on 'localhost:3306' (111 Connection refused) wait mysql ready ERROR 2003 (HY000): Can't connect to MySQL server on '127.1' (111) 2025-05-28T05:12:07.398108Z mysqld_safe Logging to '/data/mysql/log/alert.log'. 2025-05-28T05:12:07.413673Z mysqld_safe Starting mysqld daemon with databases from /data/mysql/data wait mysql ready ERROR 2003 (HY000): Can't connect to MySQL server on '127.1' (111) wait mysql ready ERROR 2003 (HY000): Can't connect to MySQL server on '127.1' (111) wait mysql ready 1 1 mysql is ok 2025-05-28 05:12:57,202 - AuditController - INFO - Created a mysql connection pool with size = 3. 2025-05-28 05:12:57,202 - AuditController - INFO - Starting a Label Check Thread to listen k8s' audit label every 10 second. 2025-05-28 05:12:57,202 - AuditController - INFO - Starting a Log Flush Thread to flush audit log every 1 second. cluster logs specify instance and container `kbcli cluster logs px-sdv --tail 30 --instance px-sdv-gms-0 -c exporter --namespace default ` ts=2025-05-28T05:12:00.818Z caller=mysqld_exporter.go:277 level=info msg="Starting mysqld_exporter" version="(version=0.14.0, branch=HEAD, revision=ca1b9af82a471c849c529eb8aadb1aac73e7b68c)" ts=2025-05-28T05:12:00.818Z caller=mysqld_exporter.go:278 level=info msg="Build context" (gogo1.17.8,userroot@401d370ca42e,date20220304-16:25:15)=(MISSING) ts=2025-05-28T05:12:00.818Z caller=mysqld_exporter.go:293 level=info msg="Scraper enabled" scraper=slave_status ts=2025-05-28T05:12:00.818Z caller=mysqld_exporter.go:293 level=info msg="Scraper enabled" scraper=global_status ts=2025-05-28T05:12:00.819Z caller=mysqld_exporter.go:293 level=info msg="Scraper enabled" scraper=global_variables ts=2025-05-28T05:12:00.819Z caller=mysqld_exporter.go:293 level=info msg="Scraper enabled" scraper=info_schema.innodb_cmp ts=2025-05-28T05:12:00.819Z caller=mysqld_exporter.go:293 level=info msg="Scraper enabled" scraper=info_schema.innodb_cmpmem ts=2025-05-28T05:12:00.819Z caller=mysqld_exporter.go:293 level=info msg="Scraper enabled" scraper=info_schema.query_response_time ts=2025-05-28T05:12:00.819Z caller=mysqld_exporter.go:303 level=info msg="Listening on address" address=:9104 ts=2025-05-28T05:12:00.819Z caller=tls_config.go:195 level=info msg="TLS is disabled." http2=false delete cluster px-sdv `kbcli cluster delete px-sdv --auto-approve --namespace default ` Cluster px-sdv deleted pod_info:px-sdv-cdc-0 2/2 Terminating 0 6m51s px-sdv-cn-0 2/2 Running 0 6m51s px-sdv-dn-0 3/3 Running 0 6m51s px-sdv-dn-1 3/3 Running 0 6m px-sdv-dn-2 3/3 Running 0 5m9s px-sdv-gms-0 3/3 Running 0 6m51s px-sdv-gms-1 3/3 Running 0 6m10s px-sdv-gms-2 3/3 Running 0 5m28s pod_info:px-sdv-dn-0 3/3 Terminating 0 7m11s px-sdv-dn-1 3/3 Terminating 0 6m20s px-sdv-dn-2 3/3 Terminating 0 5m29s px-sdv-gms-0 3/3 Terminating 0 7m11s px-sdv-gms-1 3/3 Terminating 0 6m30s px-sdv-gms-2 3/3 Terminating 0 5m48s No resources found in default namespace. delete cluster pod done No resources found in default namespace. check cluster resource non-exist OK: pvc No resources found in default namespace. delete cluster done No resources found in default namespace. No resources found in default namespace. No resources found in default namespace. Polardbx Test Suite All Done! --------------------------------------Polardbx (Topology = Replicas 3) Test Result-------------------------------------- [PASSED]|[Create]|[ComponentDefinition=polardbx-cdc-1.0.0-alpha.0;ComponentVersion=polardbx-cdc;ServiceVersion=2.3.0;]|[Description=Create a cluster with the specified component definition polardbx-cdc-1.0.0-alpha.0 and component version polardbx-cdc and service version 2.3.0] [PASSED]|[Update]|[Monitor=true]|[Description=Update the cluster Monitor enable] [PASSED]|[VerticalScaling]|[ComponentName=cn,cdc]|[Description=VerticalScaling the cluster specify component cn,cdc] [PASSED]|[Restart]|[ComponentName=cn,cdc]|[Description=Restart the cluster specify component cn,cdc] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [PASSED]|[VolumeExpansion]|[ComponentName=gms,dn]|[Description=VolumeExpansion the cluster specify component gms,dn] [PASSED]|[HorizontalScaling Out]|[ComponentName=cn,cdc]|[Description=HorizontalScaling Out the cluster specify component cn,cdc] [PASSED]|[HorizontalScaling In]|[ComponentName=cn,cdc]|[Description=HorizontalScaling In the cluster specify component cn,cdc] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]