CURRENT_TEST_DIR:/Users/huangzhangshu/projects/apecloud/github/testinfra/test/kbcli source commons files source engines files source kubeblocks files source kubedb files CLUSTER_NAME: check registry secret docker registry secret kbcli-test-registry-key already exists check ns:default sa:default imagePullSecrets ns:default sa:default imagePullSecrets kbcli-test-registry-key already exists 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.1 skip upgrade KubeBlocks current KubeBlocks version: 1.0.1 check component definition No resources found KUBEBLOCKS NAMESPACE:kb-system get kubeblocks namespace done annotate goldendb cmpd apps.kubeblocks.io/skip-immutable-check=true No resources found KUBEBLOCKS NAMESPACE:kb-system get kubeblocks namespace done current KubeBlocks version: 1.0.1 `helm upgrade --install --namespace kb-system kb-addon-goldendb kbcli-test-enterprise/goldendb --version 1.0.1 --set image.registry=apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com --set images.registry=apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com --set extra.keepResource=false ` Release "kb-addon-goldendb" does not exist. Installing it now. NAME: kb-addon-goldendb LAST DEPLOYED: Fri Sep 12 14:05:25 2025 NAMESPACE: kb-system STATUS: deployed REVISION: 1 NOTES: Release Information: Commit ID: "f15ce3cde665a2b7bcde8a001b8e57323784fcad" Commit Time: "2025-09-11 15:55:51 +0800" Release Branch: "v1.0.1" Release Time: "2025-09-11 16:33:48 +0800" Enterprise: "true" KUBEBLOCKS NAMESPACE:kb-system get kubeblocks namespace done patch goldendb cmpd imagePullSecrets componentdefinition.apps.kubeblocks.io/golden-cn-6.1 patched componentdefinition.apps.kubeblocks.io/golden-dn-6.1 patched componentdefinition.apps.kubeblocks.io/golden-gtm-6.1 patched componentdefinition.apps.kubeblocks.io/golden-lds-6.1 patched componentdefinition.apps.kubeblocks.io/golden-manager-6.1 patched componentdefinition.apps.kubeblocks.io/golden-zk-6.1 patched KUBEBLOCKS NAMESPACE:kb-system get kubeblocks namespace done annotate goldendb cmpd apps.kubeblocks.io/skip-immutable-check=true componentdefinition.apps.kubeblocks.io/golden-cn-6.1 annotated componentdefinition.apps.kubeblocks.io/golden-dn-6.1 annotated componentdefinition.apps.kubeblocks.io/golden-gtm-6.1 annotated componentdefinition.apps.kubeblocks.io/golden-lds-6.1 annotated componentdefinition.apps.kubeblocks.io/golden-manager-6.1 annotated componentdefinition.apps.kubeblocks.io/golden-zk-6.1 annotated set component version set component version:goldendb-cluster set service versions:6.1.3 set service versions sorted:6.1.3 check component definition goldendb status done set component name:goldendb-dn-00 found component version set goldendb component definition REPORT_COUNT 0: 0 set replicas first:2,6.1.3 set replicas third:2,6.1.3 set replicas fourth:2,6.1.3 set minimum cmpv service version set minimum cmpv service version replicas:2,6.1.3 REPORT_COUNT:1 CLUSTER_TOPOLOGY:goldendb-cluster topology goldendb-cluster found in cluster definition goldendb set goldendb component definition LIMIT_CPU:1 LIMIT_MEMORY:1 storage size: 20 CLUSTER_NAME:goldendb-flhwvy No resources found in default namespace. pod_info: termination_policy:DoNotTerminate create 2 replica DoNotTerminate goldendb cluster check component definition set component definition by component version check cmpd by labels set component definition1: golden-cn-6.1 by component version:goldendb-cluster apiVersion: apps.kubeblocks.io/v1 kind: Cluster metadata: name: goldendb-flhwvy namespace: default spec: clusterDef: goldendb topology: goldendb-cluster terminationPolicy: DoNotTerminate componentSpecs: - name: goldendb-dn-00 serviceVersion: 6.1.3 annotations: "gdb.timezone": Asia/Shanghai env: - name: TZ value: Asia/Shanghai volumes: - name: localtime hostPath: path: /usr/share/zoneinfo/Asia/Shanghai type: File replicas: 2 resources: limits: cpu: 1000m memory: 2Gi requests: cpu: 1000m memory: 2Gi volumeClaimTemplates: - name: backup spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: data-agent spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: data-log-mysql-log spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: data-mysql-data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: goldendb-cn-00 serviceVersion: 6.1.3 annotations: "gdb.timezone": Asia/Shanghai env: - name: TZ value: Asia/Shanghai volumes: - name: localtime hostPath: path: /usr/share/zoneinfo/Asia/Shanghai type: File replicas: 2 resources: limits: cpu: 1000m memory: 3Gi requests: cpu: 1000m memory: 3Gi volumeClaimTemplates: - name: data-agent spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: data-cn spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: goldendb-zk serviceVersion: 6.1.3 annotations: "gdb.timezone": Asia/Shanghai env: - name: TZ value: Asia/Shanghai volumes: - name: localtime hostPath: path: /usr/share/zoneinfo/Asia/Shanghai type: File replicas: 3 resources: limits: cpu: 1000m memory: 1Gi requests: cpu: 1000m memory: 1Gi volumeClaimTemplates: - name: insight-data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: goldendb-manager serviceVersion: 6.1.3 annotations: "gdb.timezone": Asia/Shanghai env: - name: TZ value: Asia/Shanghai volumes: - name: localtime hostPath: path: /usr/share/zoneinfo/Asia/Shanghai type: File replicas: 1 resources: limits: cpu: 3000m memory: 8Gi requests: cpu: 3000m memory: 8Gi volumeClaimTemplates: - name: insight-data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: manager-data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: omm-data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: goldendb-gtm-0 serviceVersion: 6.1.3 annotations: "gdb.timezone": Asia/Shanghai env: - name: TZ value: Asia/Shanghai volumes: - name: localtime hostPath: path: /usr/share/zoneinfo/Asia/Shanghai type: File replicas: 1 resources: limits: cpu: 1000m memory: 1Gi requests: cpu: 1000m memory: 1Gi volumeClaimTemplates: - name: data-agent spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - name: data-gtm spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi `kubectl apply -f test_create_goldendb-flhwvy.yaml` cluster.apps.kubeblocks.io/goldendb-flhwvy created apply test_create_goldendb-flhwvy.yaml Success `rm -rf test_create_goldendb-flhwvy.yaml` `kubectl get serviceaccount --no-headers --namespace default -l app.kubernetes.io/instance=goldendb-flhwvy` patch ns:default sa:kb-golden-zk-6.1 imagePullSecrets serviceaccount/kb-golden-zk-6.1 patched patch ns:default sa:kb-golden-zk-6.1 imagePullSecrets Success check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Creating Sep 12,2025 14:05 UTC+0800 clusterdefinition.kubeblocks.io/name=goldendb cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating 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 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 goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:14 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 14:19 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 14:25 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.18/192.168.0.18 Sep 12,2025 14:26 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1 / 1 1Gi / 1Gi data-agent:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:14 UTC+0800 data-gtm:20Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3 / 3 8Gi / 8Gi insight-data:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 14:14 UTC+0800 manager-data:20Gi omm-data:20Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1 / 1 1Gi / 1Gi insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:05 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1 / 1 1Gi / 1Gi insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:09 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1 / 1 1Gi / 1Gi insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:13 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-0 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-1 connect unsupported engine type: goldendb golden-cn-6.1 `kubectl get secrets -l app.kubernetes.io/instance=goldendb-flhwvy` set secret: goldendb-flhwvy-goldendb-dn-00-account-dbproxy `kubectl get secrets goldendb-flhwvy-goldendb-dn-00-account-dbproxy -o jsonpath="{.data.username}"` `kubectl get secrets goldendb-flhwvy-goldendb-dn-00-account-dbproxy -o jsonpath="{.data.password}"` `kubectl get secrets goldendb-flhwvy-goldendb-dn-00-account-dbproxy -o jsonpath="{.data.port}"` DB_USERNAME:dbproxy;DB_PASSWORD:T1KSH3dT@6W#hH03B#Qr;DB_PORT:;DB_DATABASE: check pod goldendb-flhwvy-goldendb-dn-00-0 container_name dn exist password T1KSH3dT@6W#hH03B#Qr check pod goldendb-flhwvy-goldendb-dn-00-0 container_name kbagent exist password T1KSH3dT@6W#hH03B#Qr No container logs contain secret password. describe cluster `kbcli cluster describe goldendb-flhwvy --namespace default ` Name: goldendb-flhwvy Created Time: Sep 12,2025 14:05 UTC+0800 NAMESPACE CLUSTER-DEFINITION TOPOLOGY STATUS TERMINATION-POLICY default goldendb goldendb-cluster Running DoNotTerminate Endpoints: COMPONENT INTERNAL EXTERNAL goldendb-cn-00 goldendb-flhwvy-goldendb-cn-00-proxy.default.svc.cluster.local:8880 goldendb-zk goldendb-flhwvy-goldendb-zk.default.svc.cluster.local:32181 Topology: COMPONENT SERVICE-VERSION INSTANCE ROLE STATUS AZ NODE CREATED-TIME goldendb-cn-00 6.1.3 goldendb-flhwvy-goldendb-cn-00-0 Running cn-guangzhou-b 192.168.0.13/192.168.0.13 Sep 12,2025 14:14 UTC+0800 goldendb-cn-00 6.1.3 goldendb-flhwvy-goldendb-cn-00-1 Running cn-guangzhou-b 192.168.0.50/192.168.0.50 Sep 12,2025 14:19 UTC+0800 goldendb-dn-00 6.1.3 goldendb-flhwvy-goldendb-dn-00-0 primary Running cn-guangzhou-b 192.168.0.50/192.168.0.50 Sep 12,2025 14:25 UTC+0800 goldendb-dn-00 6.1.3 goldendb-flhwvy-goldendb-dn-00-1 standby Running cn-guangzhou-b 192.168.0.18/192.168.0.18 Sep 12,2025 14:26 UTC+0800 goldendb-gtm-0 6.1.3 goldendb-flhwvy-goldendb-gtm-0-0 primary Running cn-guangzhou-b 192.168.0.12/192.168.0.12 Sep 12,2025 14:14 UTC+0800 goldendb-manager 6.1.3 goldendb-flhwvy-goldendb-manager-0 Running cn-guangzhou-b 192.168.0.50/192.168.0.50 Sep 12,2025 14:14 UTC+0800 goldendb-zk 6.1.3 goldendb-flhwvy-goldendb-zk-0 Running cn-guangzhou-b 192.168.0.12/192.168.0.12 Sep 12,2025 14:05 UTC+0800 goldendb-zk 6.1.3 goldendb-flhwvy-goldendb-zk-1 Running cn-guangzhou-b 192.168.0.13/192.168.0.13 Sep 12,2025 14:09 UTC+0800 goldendb-zk 6.1.3 goldendb-flhwvy-goldendb-zk-2 Running cn-guangzhou-b 192.168.0.13/192.168.0.13 Sep 12,2025 14:13 UTC+0800 Resources Allocation: COMPONENT INSTANCE-TEMPLATE CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS goldendb-cn-00 1 / 1 3Gi / 3Gi data-agent:20Gi ebs-ssd data-cn:20Gi ebs-ssd goldendb-dn-00 1 / 1 2Gi / 2Gi backup:20Gi ebs-ssd data-agent:20Gi ebs-ssd data-log-mysql-log:20Gi ebs-ssd data-mysql-data:20Gi ebs-ssd goldendb-gtm-0 1 / 1 1Gi / 1Gi data-agent:20Gi ebs-ssd data-gtm:20Gi ebs-ssd goldendb-manager 3 / 3 8Gi / 8Gi insight-data:20Gi ebs-ssd manager-data:20Gi ebs-ssd omm-data:20Gi ebs-ssd goldendb-zk 1 / 1 1Gi / 1Gi insight-data:20Gi ebs-ssd Images: COMPONENT COMPONENT-DEFINITION IMAGE goldendb-cn-00 golden-cn-6.1 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/goldendb-cn:6.1.03.08 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/goldendb-dn:6.1.03.08 goldendb-dn-00 golden-dn-6.1 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/goldendb-dn:6.1.03.08 goldendb-gtm-0 golden-gtm-6.1 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/goldendb-gtm:6.1.03.08 goldendb-manager golden-manager-6.1 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/goldendb-control:6.1.03.08 goldendb-zk golden-zk-6.1 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/goldendb-zk:6.1.03.08 Data Protection: BACKUP-REPO AUTO-BACKUP BACKUP-SCHEDULE BACKUP-METHOD BACKUP-RETENTION RECOVERABLE-TIME backuprepo-kbcli-test Enabled 0 2 */1 * * full 7d Show cluster events: kbcli cluster list-events -n default goldendb-flhwvy `kbcli cluster label goldendb-flhwvy app.kubernetes.io/instance- --namespace default ` label "app.kubernetes.io/instance" not found. `kbcli cluster label goldendb-flhwvy app.kubernetes.io/instance=goldendb-flhwvy --namespace default ` `kbcli cluster label goldendb-flhwvy --list --namespace default ` NAME NAMESPACE LABELS goldendb-flhwvy default app.kubernetes.io/instance=goldendb-flhwvy clusterdefinition.kubeblocks.io/name=goldendb label cluster app.kubernetes.io/instance=goldendb-flhwvy Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=goldendb-flhwvy --namespace default ` `kbcli cluster label goldendb-flhwvy --list --namespace default ` NAME NAMESPACE LABELS goldendb-flhwvy default app.kubernetes.io/instance=goldendb-flhwvy case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=goldendb label cluster case.name=kbcli.test1 Success `kbcli cluster label goldendb-flhwvy case.name=kbcli.test2 --overwrite --namespace default ` `kbcli cluster label goldendb-flhwvy --list --namespace default ` NAME NAMESPACE LABELS goldendb-flhwvy default app.kubernetes.io/instance=goldendb-flhwvy case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=goldendb label cluster case.name=kbcli.test2 Success `kbcli cluster label goldendb-flhwvy case.name- --namespace default ` `kbcli cluster label goldendb-flhwvy --list --namespace default ` NAME NAMESPACE LABELS goldendb-flhwvy default app.kubernetes.io/instance=goldendb-flhwvy clusterdefinition.kubeblocks.io/name=goldendb delete cluster label case.name Success cluster connect kbcli unsupported engine type: goldendb-dn-00 LB_TYPE is set to: intranet cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose goldendb-flhwvy --auto-approve --force=true --type intranet --enable true --components goldendb-dn-00 --role-selector primary --namespace default ` OpsRequest goldendb-flhwvy-expose-htqjm created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-expose-htqjm -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-expose-htqjm default Expose goldendb-flhwvy goldendb-dn-00 Running 0/1 Sep 12,2025 14:42 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Running Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:14 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 14:19 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 14:25 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.18/192.168.0.18 Sep 12,2025 14:26 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1 / 1 1Gi / 1Gi data-agent:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:14 UTC+0800 data-gtm:20Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3 / 3 8Gi / 8Gi insight-data:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 14:14 UTC+0800 manager-data:20Gi omm-data:20Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1 / 1 1Gi / 1Gi insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:05 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1 / 1 1Gi / 1Gi insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:09 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1 / 1 1Gi / 1Gi insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:13 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-0 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-1 connect unsupported engine type: goldendb golden-cn-6.1 check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-expose-htqjm default Expose goldendb-flhwvy goldendb-dn-00 Running 0/1 Sep 12,2025 14:42 UTC+0800 ops_status:goldendb-flhwvy-expose-htqjm default Expose goldendb-flhwvy goldendb-dn-00 Running 0/1 Sep 12,2025 14:42 UTC+0800 check ops status done ops_status:goldendb-flhwvy-expose-htqjm default Expose goldendb-flhwvy goldendb-dn-00 Succeed 1/1 Sep 12,2025 14:42 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-expose-htqjm --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-expose-htqjm patched `kbcli cluster delete-ops --name goldendb-flhwvy-expose-htqjm --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-expose-htqjm deleted check component goldendb-dn-00 exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-dn-00 --namespace default | (grep "goldendb-dn-00" || true )` check component goldendb-cn-00 exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-cn-00 --namespace default | (grep "goldendb-cn-00" || true )` cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart goldendb-flhwvy --auto-approve --force=true --components goldendb-dn-00,goldendb-cn-00 --namespace default ` OpsRequest goldendb-flhwvy-restart-xn4ns created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-restart-xn4ns -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-restart-xn4ns default Restart goldendb-flhwvy goldendb-dn-00,goldendb-cn-00 Running 0/4 Sep 12,2025 14:43 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:50 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 14:43 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:50 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 14:43 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1 / 1 1Gi / 1Gi data-agent:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:14 UTC+0800 data-gtm:20Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3 / 3 8Gi / 8Gi insight-data:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 14:14 UTC+0800 manager-data:20Gi omm-data:20Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1 / 1 1Gi / 1Gi insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:05 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1 / 1 1Gi / 1Gi insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:09 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1 / 1 1Gi / 1Gi insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:13 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-1 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-0 connect unsupported engine type: goldendb golden-cn-6.1 check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-restart-xn4ns default Restart goldendb-flhwvy goldendb-dn-00,goldendb-cn-00 Succeed 4/4 Sep 12,2025 14:43 UTC+0800 check ops status done ops_status:goldendb-flhwvy-restart-xn4ns default Restart goldendb-flhwvy goldendb-dn-00,goldendb-cn-00 Succeed 4/4 Sep 12,2025 14:43 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-restart-xn4ns --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-restart-xn4ns patched `kbcli cluster delete-ops --name goldendb-flhwvy-restart-xn4ns --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-restart-xn4ns deleted check component goldendb-zk exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-zk --namespace default | (grep "goldendb-zk" || true )` check component goldendb-gtm-0 exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-gtm-0 --namespace default | (grep "goldendb-gtm-0" || true )` check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale goldendb-flhwvy --auto-approve --force=true --components goldendb-zk,goldendb-gtm-0 --cpu 1100m --memory 1.1Gi --namespace default ` OpsRequest goldendb-flhwvy-verticalscaling-7fsmz created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-verticalscaling-7fsmz -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-verticalscaling-7fsmz default VerticalScaling goldendb-flhwvy goldendb-zk,goldendb-gtm-0 Running 0/4 Sep 12,2025 14:51 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 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 cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:50 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 14:43 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:50 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 14:43 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:51 UTC+0800 data-gtm:20Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3 / 3 8Gi / 8Gi insight-data:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 14:14 UTC+0800 manager-data:20Gi omm-data:20Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:54 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:53 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:51 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-1 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-0 connect unsupported engine type: goldendb golden-cn-6.1 check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-verticalscaling-7fsmz default VerticalScaling goldendb-flhwvy goldendb-zk,goldendb-gtm-0 Succeed 4/4 Sep 12,2025 14:51 UTC+0800 check ops status done ops_status:goldendb-flhwvy-verticalscaling-7fsmz default VerticalScaling goldendb-flhwvy goldendb-zk,goldendb-gtm-0 Succeed 4/4 Sep 12,2025 14:51 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-verticalscaling-7fsmz --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-verticalscaling-7fsmz patched `kbcli cluster delete-ops --name goldendb-flhwvy-verticalscaling-7fsmz --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-verticalscaling-7fsmz deleted check component goldendb-gtm-0 exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-gtm-0 --namespace default | (grep "goldendb-gtm-0" || true )` `kubectl get pvc -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-gtm-0,apps.kubeblocks.io/vct-name=data-agent,data-gtm --namespace default ` No resources found in default namespace. goldendb-flhwvy goldendb-gtm-0 data-agent,data-gtm pvc is empty cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in goldendb-flhwvy namespace. `kbcli cluster volume-expand goldendb-flhwvy --auto-approve --force=true --components goldendb-gtm-0 --volume-claim-templates data-agent,data-gtm --storage 23Gi --namespace default ` OpsRequest goldendb-flhwvy-volumeexpansion-r2gsf created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-volumeexpansion-r2gsf -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-volumeexpansion-r2gsf default VolumeExpansion goldendb-flhwvy goldendb-gtm-0 Running 0/2 Sep 12,2025 14:55 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:50 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 14:43 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:50 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 14:43 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:51 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3 / 3 8Gi / 8Gi insight-data:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 14:14 UTC+0800 manager-data:20Gi omm-data:20Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:54 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:53 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:51 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-1 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-0 connect unsupported engine type: goldendb golden-cn-6.1 No resources found in goldendb-flhwvy namespace. check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-volumeexpansion-r2gsf default VolumeExpansion goldendb-flhwvy goldendb-gtm-0 Succeed 2/2 Sep 12,2025 14:55 UTC+0800 check ops status done ops_status:goldendb-flhwvy-volumeexpansion-r2gsf default VolumeExpansion goldendb-flhwvy goldendb-gtm-0 Succeed 2/2 Sep 12,2025 14:55 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-volumeexpansion-r2gsf --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-volumeexpansion-r2gsf patched `kbcli cluster delete-ops --name goldendb-flhwvy-volumeexpansion-r2gsf --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-volumeexpansion-r2gsf deleted check component goldendb-manager exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-manager --namespace default | (grep "goldendb-manager" || true )` check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster update goldendb-flhwvy --namespace default ` cluster.apps.kubeblocks.io/goldendb-flhwvy updated (no change) check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 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 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 check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:50 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 14:43 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:50 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 14:43 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:51 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:15 UTC+0800 manager-data:20Gi omm-data:20Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:54 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:53 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:51 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-1 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-0 connect unsupported engine type: goldendb golden-cn-6.1 check component goldendb-manager exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-manager --namespace default | (grep "goldendb-manager" || true )` `kubectl get pvc -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-manager,apps.kubeblocks.io/vct-name=insight-data,manager-data,omm-data --namespace default ` No resources found in default namespace. goldendb-flhwvy goldendb-manager insight-data,manager-data,omm-data pvc is empty cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in goldendb-flhwvy namespace. `kbcli cluster volume-expand goldendb-flhwvy --auto-approve --force=true --components goldendb-manager --volume-claim-templates insight-data,manager-data,omm-data --storage 26Gi --namespace default ` OpsRequest goldendb-flhwvy-volumeexpansion-n5c6s created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-volumeexpansion-n5c6s -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-volumeexpansion-n5c6s default VolumeExpansion goldendb-flhwvy goldendb-manager Running 0/3 Sep 12,2025 15:20 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:50 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 14:43 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:50 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 14:43 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:51 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:15 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:54 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 14:53 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 14:51 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-1 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-0 connect unsupported engine type: goldendb golden-cn-6.1 No resources found in goldendb-flhwvy namespace. check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-volumeexpansion-n5c6s default VolumeExpansion goldendb-flhwvy goldendb-manager Succeed 3/3 Sep 12,2025 15:20 UTC+0800 check ops status done ops_status:goldendb-flhwvy-volumeexpansion-n5c6s default VolumeExpansion goldendb-flhwvy goldendb-manager Succeed 3/3 Sep 12,2025 15:20 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-volumeexpansion-n5c6s --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-volumeexpansion-n5c6s patched `kbcli cluster delete-ops --name goldendb-flhwvy-volumeexpansion-n5c6s --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-volumeexpansion-n5c6s deleted cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop goldendb-flhwvy --auto-approve --force=true --namespace default ` OpsRequest goldendb-flhwvy-stop-28z9f created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-stop-28z9f -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-stop-28z9f default Stop goldendb-flhwvy goldendb-cn-00,goldendb-dn-00,goldendb-gtm-0,goldendb-manager,goldendb-zk Running 0/9 Sep 12,2025 15:21 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Stopping Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping 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 goldendb-flhwvy --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 goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-stop-28z9f default Stop goldendb-flhwvy goldendb-cn-00,goldendb-dn-00,goldendb-gtm-0,goldendb-manager,goldendb-zk Succeed 9/9 Sep 12,2025 15:21 UTC+0800 check ops status done ops_status:goldendb-flhwvy-stop-28z9f default Stop goldendb-flhwvy goldendb-cn-00,goldendb-dn-00,goldendb-gtm-0,goldendb-manager,goldendb-zk Succeed 9/9 Sep 12,2025 15:21 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-stop-28z9f --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-stop-28z9f patched `kbcli cluster delete-ops --name goldendb-flhwvy-stop-28z9f --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-stop-28z9f deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start goldendb-flhwvy --force=true --namespace default ` OpsRequest goldendb-flhwvy-start-r48b9 created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-start-r48b9 -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-start-r48b9 default Start goldendb-flhwvy goldendb-cn-00,goldendb-dn-00,goldendb-gtm-0,goldendb-manager,goldendb-zk Running 0/9 Sep 12,2025 15:23 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 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 goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:23 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:24 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:24 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-0 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-1 connect unsupported engine type: goldendb golden-cn-6.1 check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-start-r48b9 default Start goldendb-flhwvy goldendb-cn-00,goldendb-dn-00,goldendb-gtm-0,goldendb-manager,goldendb-zk Succeed 9/9 Sep 12,2025 15:23 UTC+0800 check ops status done ops_status:goldendb-flhwvy-start-r48b9 default Start goldendb-flhwvy goldendb-cn-00,goldendb-dn-00,goldendb-gtm-0,goldendb-manager,goldendb-zk Succeed 9/9 Sep 12,2025 15:23 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-start-r48b9 --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-start-r48b9 patched `kbcli cluster delete-ops --name goldendb-flhwvy-start-r48b9 --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-start-r48b9 deleted check component goldendb-cn-00 exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-cn-00 --namespace default | (grep "goldendb-cn-00" || true )` cluster goldendb-cn-00 scale-out check cluster status before ops check cluster status done cluster_status:Running No resources found in goldendb-flhwvy namespace. `kbcli cluster scale-out goldendb-flhwvy --auto-approve --force=true --components goldendb-cn-00 --replicas 1 --namespace default ` OpsRequest goldendb-flhwvy-horizontalscaling-n6ks2 created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-horizontalscaling-n6ks2 -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-horizontalscaling-n6ks2 default HorizontalScaling goldendb-flhwvy goldendb-cn-00 Running 0/1 Sep 12,2025 15:25 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 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 goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-2 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:25 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:23 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:24 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:24 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-0 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-1 connect unsupported engine type: goldendb golden-cn-6.1 No resources found in goldendb-flhwvy namespace. check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-horizontalscaling-n6ks2 default HorizontalScaling goldendb-flhwvy goldendb-cn-00 Succeed 1/1 Sep 12,2025 15:25 UTC+0800 check ops status done ops_status:goldendb-flhwvy-horizontalscaling-n6ks2 default HorizontalScaling goldendb-flhwvy goldendb-cn-00 Succeed 1/1 Sep 12,2025 15:25 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-horizontalscaling-n6ks2 --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-horizontalscaling-n6ks2 patched `kbcli cluster delete-ops --name goldendb-flhwvy-horizontalscaling-n6ks2 --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-horizontalscaling-n6ks2 deleted check component goldendb-cn-00 exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-cn-00 --namespace default | (grep "goldendb-cn-00" || true )` cluster goldendb-cn-00 scale-in check cluster status before ops check cluster status done cluster_status:Running No resources found in goldendb-flhwvy namespace. `kbcli cluster scale-in goldendb-flhwvy --auto-approve --force=true --components goldendb-cn-00 --replicas 1 --namespace default ` OpsRequest goldendb-flhwvy-horizontalscaling-cj742 created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-horizontalscaling-cj742 -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-horizontalscaling-cj742 default HorizontalScaling goldendb-flhwvy goldendb-cn-00 Running -/- Sep 12,2025 15:27 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:23 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:24 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:24 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-0 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-1 connect unsupported engine type: goldendb golden-cn-6.1 No resources found in goldendb-flhwvy namespace. check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-horizontalscaling-cj742 default HorizontalScaling goldendb-flhwvy goldendb-cn-00 Succeed 1/1 Sep 12,2025 15:27 UTC+0800 check ops status done ops_status:goldendb-flhwvy-horizontalscaling-cj742 default HorizontalScaling goldendb-flhwvy goldendb-cn-00 Succeed 1/1 Sep 12,2025 15:27 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-horizontalscaling-cj742 --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-horizontalscaling-cj742 patched `kbcli cluster delete-ops --name goldendb-flhwvy-horizontalscaling-cj742 --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-horizontalscaling-cj742 deleted check component goldendb-zk exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-zk --namespace default | (grep "goldendb-zk" || true )` `kubectl get pvc -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-zk,apps.kubeblocks.io/vct-name=insight-data --namespace default ` cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in goldendb-flhwvy namespace. `kbcli cluster volume-expand goldendb-flhwvy --auto-approve --force=true --components goldendb-zk --volume-claim-templates insight-data --storage 21Gi --namespace default ` OpsRequest goldendb-flhwvy-volumeexpansion-9b8t4 created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-volumeexpansion-9b8t4 -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-volumeexpansion-9b8t4 default VolumeExpansion goldendb-flhwvy goldendb-zk Running 0/3 Sep 12,2025 15:28 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-cn:20Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:23 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:24 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:24 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-0 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-1 connect unsupported engine type: goldendb golden-cn-6.1 No resources found in goldendb-flhwvy namespace. check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-volumeexpansion-9b8t4 default VolumeExpansion goldendb-flhwvy goldendb-zk Succeed 3/3 Sep 12,2025 15:28 UTC+0800 check ops status done ops_status:goldendb-flhwvy-volumeexpansion-9b8t4 default VolumeExpansion goldendb-flhwvy goldendb-zk Succeed 3/3 Sep 12,2025 15:28 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-volumeexpansion-9b8t4 --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-volumeexpansion-9b8t4 patched `kbcli cluster delete-ops --name goldendb-flhwvy-volumeexpansion-9b8t4 --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-volumeexpansion-9b8t4 deleted check component goldendb-cn-00 exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-cn-00 --namespace default | (grep "goldendb-cn-00" || true )` `kubectl get pvc -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-cn-00,apps.kubeblocks.io/vct-name=data-agent,data-cn --namespace default ` No resources found in default namespace. goldendb-flhwvy goldendb-cn-00 data-agent,data-cn pvc is empty cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in goldendb-flhwvy namespace. `kbcli cluster volume-expand goldendb-flhwvy --auto-approve --force=true --components goldendb-cn-00 --volume-claim-templates data-agent,data-cn --storage 25Gi --namespace default ` OpsRequest goldendb-flhwvy-volumeexpansion-d7rsg created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-volumeexpansion-d7rsg -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-volumeexpansion-d7rsg default VolumeExpansion goldendb-flhwvy goldendb-cn-00 Running 0/4 Sep 12,2025 15:29 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:25Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:25Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:23 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:24 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:24 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-0 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-1 connect unsupported engine type: goldendb golden-cn-6.1 No resources found in goldendb-flhwvy namespace. check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-volumeexpansion-d7rsg default VolumeExpansion goldendb-flhwvy goldendb-cn-00 Succeed 4/4 Sep 12,2025 15:29 UTC+0800 check ops status done ops_status:goldendb-flhwvy-volumeexpansion-d7rsg default VolumeExpansion goldendb-flhwvy goldendb-cn-00 Succeed 4/4 Sep 12,2025 15:29 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-volumeexpansion-d7rsg --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-volumeexpansion-d7rsg patched `kbcli cluster delete-ops --name goldendb-flhwvy-volumeexpansion-d7rsg --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-volumeexpansion-d7rsg deleted cluster does not need to check monitor currently check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Running Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:25Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1 / 1 3Gi / 3Gi data-agent:25Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:23 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:24 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:24 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-0 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-1 connect unsupported engine type: goldendb golden-cn-6.1 check component goldendb-cn-00 exists `kubectl get components -l app.kubernetes.io/instance=goldendb-flhwvy,apps.kubeblocks.io/component-name=goldendb-cn-00 --namespace default | (grep "goldendb-cn-00" || true )` check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale goldendb-flhwvy --auto-approve --force=true --components goldendb-cn-00 --cpu 1100m --memory 3.1Gi --namespace default ` OpsRequest goldendb-flhwvy-verticalscaling-2h6rz created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-verticalscaling-2h6rz -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-verticalscaling-2h6rz default VerticalScaling goldendb-flhwvy goldendb-cn-00 Running 0/2 Sep 12,2025 15:30 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 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 check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1100m / 1100m 3328599654400m / 3328599654400m data-agent:25Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:32 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1100m / 1100m 3328599654400m / 3328599654400m data-agent:25Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:30 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1 / 1 2Gi / 2Gi backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:23 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:23 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:24 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:24 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-0 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-1 connect unsupported engine type: goldendb golden-cn-6.1 check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-verticalscaling-2h6rz default VerticalScaling goldendb-flhwvy goldendb-cn-00 Succeed 2/2 Sep 12,2025 15:30 UTC+0800 check ops status done ops_status:goldendb-flhwvy-verticalscaling-2h6rz default VerticalScaling goldendb-flhwvy goldendb-cn-00 Succeed 2/2 Sep 12,2025 15:30 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-verticalscaling-2h6rz --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-verticalscaling-2h6rz patched `kbcli cluster delete-ops --name goldendb-flhwvy-verticalscaling-2h6rz --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-verticalscaling-2h6rz deleted check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale goldendb-flhwvy --auto-approve --force=true --components goldendb-dn-00 --cpu 1100m --memory 2.1Gi --namespace default ` OpsRequest goldendb-flhwvy-verticalscaling-4488g created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-verticalscaling-4488g -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-verticalscaling-4488g default VerticalScaling goldendb-flhwvy goldendb-dn-00 Running 0/2 Sep 12,2025 15:33 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 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 cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1100m / 1100m 3328599654400m / 3328599654400m data-agent:25Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:32 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1100m / 1100m 3328599654400m / 3328599654400m data-agent:25Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:30 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1100m / 1100m 2254857830400m / 2254857830400m backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:35 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1100m / 1100m 2254857830400m / 2254857830400m backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:33 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:23 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:24 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:24 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-0 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-1 connect unsupported engine type: goldendb golden-cn-6.1 check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-verticalscaling-4488g default VerticalScaling goldendb-flhwvy goldendb-dn-00 Succeed 2/2 Sep 12,2025 15:33 UTC+0800 check ops status done ops_status:goldendb-flhwvy-verticalscaling-4488g default VerticalScaling goldendb-flhwvy goldendb-dn-00 Succeed 2/2 Sep 12,2025 15:33 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-verticalscaling-4488g --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-verticalscaling-4488g patched `kbcli cluster delete-ops --name goldendb-flhwvy-verticalscaling-4488g --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-verticalscaling-4488g deleted test failover check cluster status before cluster-failover- check cluster status done cluster_status:Running delete pod:goldendb-flhwvy-goldendb-dn-00-0 `kubectl delete pod goldendb-flhwvy-goldendb-dn-00-0 --force --namespace default ` 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 "goldendb-flhwvy-goldendb-dn-00-0" force deleted check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb DoNotTerminate Updating Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb 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 goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1100m / 1100m 3328599654400m / 3328599654400m data-agent:25Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:32 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1100m / 1100m 3328599654400m / 3328599654400m data-agent:25Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:30 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1100m / 1100m 2254857830400m / 2254857830400m backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:36 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1100m / 1100m 2254857830400m / 2254857830400m backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:33 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:23 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:24 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:24 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-1 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-0 connect unsupported engine type: goldendb golden-cn-6.1 check failover pod name failover pod name:goldendb-flhwvy-goldendb-dn-00-1 failover Success cluster update terminationPolicy WipeOut `kbcli cluster update goldendb-flhwvy --termination-policy=WipeOut --namespace default ` cluster.apps.kubeblocks.io/goldendb-flhwvy updated check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb WipeOut Running Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1100m / 1100m 3328599654400m / 3328599654400m data-agent:25Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:32 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1100m / 1100m 3328599654400m / 3328599654400m data-agent:25Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:30 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1100m / 1100m 2254857830400m / 2254857830400m backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:36 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1100m / 1100m 2254857830400m / 2254857830400m backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:33 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:23 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:24 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:24 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-1 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-0 connect unsupported engine type: goldendb golden-cn-6.1 cluster list-logs `kbcli cluster list-logs goldendb-flhwvy --namespace default ` No log files found. cluster logs `kbcli cluster logs goldendb-flhwvy --tail 30 --namespace default ` Defaulted container "gtm" out of: gtm, kbagent, init-kbagent (init), kbagent-worker (init) + cp -f /opt/kb/scripts/..2025_09_12_07_23_11.54271289/cn_action.py /goldendb_config/containerStartup/ + for file in $(ls /opt/kb/scripts/*.py) ++ readlink -f /opt/kb/scripts/dbagent_action.py + linkf=/opt/kb/scripts/..2025_09_12_07_23_11.54271289/dbagent_action.py ++ basename /opt/kb/scripts/dbagent_action.py + baseName=dbagent_action.py + [[ dbagent_action.py == \r\e\s\t\o\r\e\_\d\n\.\p\y ]] + cp -f /opt/kb/scripts/..2025_09_12_07_23_11.54271289/dbagent_action.py /goldendb_config/containerStartup/ + for file in $(ls /opt/kb/scripts/*.py) ++ readlink -f /opt/kb/scripts/rdb_action.py + linkf=/opt/kb/scripts/..2025_09_12_07_23_11.54271289/rdb_action.py ++ basename /opt/kb/scripts/rdb_action.py + baseName=rdb_action.py + [[ rdb_action.py == \r\e\s\t\o\r\e\_\d\n\.\p\y ]] + cp -f /opt/kb/scripts/..2025_09_12_07_23_11.54271289/rdb_action.py /goldendb_config/containerStartup/ + for file in $(ls /opt/kb/scripts/*.py) ++ readlink -f /opt/kb/scripts/restore_dn.py + linkf=/opt/kb/scripts/..2025_09_12_07_23_11.54271289/restore_dn.py ++ basename /opt/kb/scripts/restore_dn.py + baseName=restore_dn.py + [[ restore_dn.py == \r\e\s\t\o\r\e\_\d\n\.\p\y ]] + [[ -d /home/zxdb/bin/restore_dn ]] + continue + for file in $(ls /opt/kb/scripts/*.py) ++ readlink -f /opt/kb/scripts/tls_config_reload.py + linkf=/opt/kb/scripts/..2025_09_12_07_23_11.54271289/tls_config_reload.py ++ basename /opt/kb/scripts/tls_config_reload.py + baseName=tls_config_reload.py + [[ tls_config_reload.py == \r\e\s\t\o\r\e\_\d\n\.\p\y ]] + cp -f /opt/kb/scripts/..2025_09_12_07_23_11.54271289/tls_config_reload.py /goldendb_config/containerStartup/ cluster logs specify instance and container `kbcli cluster logs goldendb-flhwvy --tail 30 --instance goldendb-flhwvy-goldendb-dn-00-1 -c kbagent --namespace default ` 2025-09-12T15:34:03+08:00 INFO create service Action {"actions": "postProvision,switchover,memberJoin,memberLeave,roleProbe"} 2025-09-12T15:34:03+08:00 INFO create service Probe {"probes": "roleProbe"} 2025-09-12T15:34:03+08:00 INFO create service Streaming {"actions": ""} 2025-09-12T15:34:03+08:00 INFO service Action started... 2025-09-12T15:34:03+08:00 INFO service Probe started... 2025-09-12T15:34:03+08:00 INFO service Streaming started... 2025-09-12T15:34:03+08:00 INFO starting the HTTP server 2025-09-12T15:34:03+08:00 INFO register service to server {"service": "Action", "method": "POST", "uri": "/v1.0/action"} 2025-09-12T15:34:03+08:00 INFO register service to server {"service": "Probe", "method": "POST", "uri": "/v1.0/probe"} 2025-09-12T15:34:03+08:00 INFO register service to server {"service": "Streaming", "method": "POST", "uri": "/v1.0/streaming"} 2025-09-12T15:34:03+08:00 INFO probe started {"probe": "roleProbe", "config": {"instance":"goldendb-flhwvy-goldendb-dn-00","action":"roleProbe","initialDelaySeconds":60,"periodSeconds":1}} 2025-09-12T15:34:03+08:00 INFO starting the streaming server 2025-09-12T15:35:03+08:00 INFO send probe event {"probe": "roleProbe", "probe": "roleProbe", "code": 0, "output": "standby", "message": ""} 2025-09-12T15:37:57+08:00 INFO send probe event {"probe": "roleProbe", "probe": "roleProbe", "code": 0, "output": "primary", "message": ""} LB_TYPE is set to: intranet cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose goldendb-flhwvy --auto-approve --force=true --type intranet --enable false --components goldendb-dn-00 --role-selector primary --namespace default ` OpsRequest goldendb-flhwvy-expose-kdjwm created successfully, you can view the progress: kbcli cluster describe-ops goldendb-flhwvy-expose-kdjwm -n default check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-expose-kdjwm default Expose goldendb-flhwvy goldendb-dn-00 Running 0/1 Sep 12,2025 15:38 UTC+0800 check cluster status `kbcli cluster list goldendb-flhwvy --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS goldendb-flhwvy default goldendb WipeOut Running Sep 12,2025 14:05 UTC+0800 app.kubernetes.io/instance=goldendb-flhwvy,clusterdefinition.kubeblocks.io/name=goldendb check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances goldendb-flhwvy --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME goldendb-flhwvy-goldendb-cn-00-0 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1100m / 1100m 3328599654400m / 3328599654400m data-agent:25Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:32 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-cn-00-1 default goldendb-flhwvy goldendb-cn-00 Running cn-guangzhou-b 1100m / 1100m 3328599654400m / 3328599654400m data-agent:25Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:30 UTC+0800 data-cn:25Gi goldendb-flhwvy-goldendb-dn-00-0 default goldendb-flhwvy goldendb-dn-00 Running standby cn-guangzhou-b 1100m / 1100m 2254857830400m / 2254857830400m backup:20Gi 192.168.0.70/192.168.0.70 Sep 12,2025 15:36 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-dn-00-1 default goldendb-flhwvy goldendb-dn-00 Running primary cn-guangzhou-b 1100m / 1100m 2254857830400m / 2254857830400m backup:20Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:33 UTC+0800 data-agent:20Gi data-log-mysql-log:20Gi data-mysql-data:20Gi goldendb-flhwvy-goldendb-gtm-0-0 default goldendb-flhwvy goldendb-gtm-0 Running primary cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m data-agent:23Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:23 UTC+0800 data-gtm:23Gi goldendb-flhwvy-goldendb-manager-0 default goldendb-flhwvy goldendb-manager Running cn-guangzhou-b 3100m / 3100m 8697308774400m / 8697308774400m insight-data:26Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 manager-data:26Gi omm-data:26Gi goldendb-flhwvy-goldendb-zk-0 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.50/192.168.0.50 Sep 12,2025 15:23 UTC+0800 goldendb-flhwvy-goldendb-zk-1 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.12/192.168.0.12 Sep 12,2025 15:24 UTC+0800 goldendb-flhwvy-goldendb-zk-2 default goldendb-flhwvy goldendb-zk Running cn-guangzhou-b 1100m / 1100m 1181116006400m / 1181116006400m insight-data:21Gi 192.168.0.13/192.168.0.13 Sep 12,2025 15:24 UTC+0800 check pod status done check cluster role check cluster role done primary: goldendb-flhwvy-goldendb-dn-00-1 goldendb-flhwvy-goldendb-gtm-0-0;standby: goldendb-flhwvy-goldendb-dn-00-0 connect unsupported engine type: goldendb golden-cn-6.1 check ops status `kbcli cluster list-ops goldendb-flhwvy --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME goldendb-flhwvy-expose-kdjwm default Expose goldendb-flhwvy goldendb-dn-00 Succeed 1/1 Sep 12,2025 15:38 UTC+0800 check ops status done ops_status:goldendb-flhwvy-expose-kdjwm default Expose goldendb-flhwvy goldendb-dn-00 Succeed 1/1 Sep 12,2025 15:38 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations goldendb-flhwvy-expose-kdjwm --namespace default ` opsrequest.operations.kubeblocks.io/goldendb-flhwvy-expose-kdjwm patched `kbcli cluster delete-ops --name goldendb-flhwvy-expose-kdjwm --force --auto-approve --namespace default ` OpsRequest goldendb-flhwvy-expose-kdjwm deleted delete cluster goldendb-flhwvy `kbcli cluster delete goldendb-flhwvy --auto-approve --namespace default ` Cluster goldendb-flhwvy deleted pod_info:goldendb-flhwvy-goldendb-cn-00-0 2/2 Running 0 6m46s goldendb-flhwvy-goldendb-cn-00-1 2/2 Running 0 8m13s goldendb-flhwvy-goldendb-dn-00-0 2/2 Running 0 2m4s goldendb-flhwvy-goldendb-dn-00-1 2/2 Running 0 5m10s goldendb-flhwvy-goldendb-gtm-0-0 2/2 Running 0 15m goldendb-flhwvy-goldendb-manager-0 2/2 Running 0 15m goldendb-flhwvy-goldendb-zk-0 1/1 Running 0 15m goldendb-flhwvy-goldendb-zk-1 1/1 Running 0 14m goldendb-flhwvy-goldendb-zk-2 1/1 Running 0 14m pod_info:goldendb-flhwvy-goldendb-cn-00-0 2/2 Terminating 0 7m7s goldendb-flhwvy-goldendb-cn-00-1 2/2 Terminating 0 8m34s goldendb-flhwvy-goldendb-dn-00-0 2/2 Terminating 0 2m25s goldendb-flhwvy-goldendb-dn-00-1 2/2 Terminating 0 5m31s goldendb-flhwvy-goldendb-gtm-0-0 2/2 Terminating 0 16m goldendb-flhwvy-goldendb-manager-0 2/2 Terminating 0 16m goldendb-flhwvy-goldendb-zk-0 1/1 Terminating 0 16m goldendb-flhwvy-goldendb-zk-1 1/1 Terminating 0 15m goldendb-flhwvy-goldendb-zk-2 1/1 Terminating 0 14m 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. GoldenDB Test Suite All Done! Test Engine: goldendb Test Type: 63 --------------------------------------GoldenDB (Topology = goldendb-cluster Replicas 2) Test Result-------------------------------------- [PASSED]|[Create]|[ComponentDefinition=golden-cn-6.1;ComponentVersion=goldendb-cluster;ServiceVersion=6.1.3;]|[Description=Create a cluster with the specified component definition golden-cn-6.1 and component version goldendb-cluster and service version 6.1.3] [PASSED]|[Expose]|[Enable=true;TYPE=intranet;ComponentName=goldendb-dn-00]|[Description=Expose Enable the intranet service with goldendb-dn-00 component] [PASSED]|[Restart]|[ComponentName=goldendb-dn-00,goldendb-cn-00]|[Description=Restart the cluster specify component goldendb-dn-00,goldendb-cn-00] [PASSED]|[VerticalScaling]|[ComponentName=goldendb-zk,goldendb-gtm-0]|[Description=VerticalScaling the cluster specify component goldendb-zk,goldendb-gtm-0] [PASSED]|[VolumeExpansion]|[ComponentName=goldendb-gtm-0]|[Description=VolumeExpansion the cluster specify component goldendb-gtm-0] [PASSED]|[Update]|[Logs=Enable]|[Description=Update the cluster Logs enable] [PASSED]|[VolumeExpansion]|[ComponentName=goldendb-manager]|[Description=VolumeExpansion the cluster specify component goldendb-manager] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [PASSED]|[HorizontalScaling Out]|[ComponentName=goldendb-cn-00]|[Description=HorizontalScaling Out the cluster specify component goldendb-cn-00] [PASSED]|[HorizontalScaling In]|[ComponentName=goldendb-cn-00]|[Description=HorizontalScaling In the cluster specify component goldendb-cn-00] [PASSED]|[VolumeExpansion]|[ComponentName=goldendb-zk]|[Description=VolumeExpansion the cluster specify component goldendb-zk] [PASSED]|[VolumeExpansion]|[ComponentName=goldendb-cn-00]|[Description=VolumeExpansion the cluster specify component goldendb-cn-00] [PASSED]|[Update]|[Monitor=true]|[Description=Update the cluster Monitor enable] [PASSED]|[VerticalScaling]|[ComponentName=goldendb-cn-00]|[Description=VerticalScaling the cluster specify component goldendb-cn-00] [PASSED]|[VerticalScaling]|[ComponentName=goldendb-dn-00]|[Description=VerticalScaling the cluster specify component goldendb-dn-00] [PASSED]|[Failover]|[HA=Delete Pod;ComponentName=goldendb-dn-00]|[Description=Simulates conditions where pods terminating forced/graceful thereby testing deployment sanity (replica availability & uninterrupted service) and recovery workflow of the application.] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Expose]|[Disable=true;TYPE=intranet;ComponentName=goldendb-dn-00]|[Description=Expose Disable the intranet service with goldendb-dn-00 component] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]