source commons files source engines files source kubeblocks files source kubedb files CLUSTER_NAME: `kubectl get namespace | grep ns-zklqi ` `kubectl create namespace ns-zklqi` namespace/ns-zklqi created create namespace ns-zklqi done download kbcli `gh release list --repo apecloud/kbcli --limit 100 | (grep "1.0" || true)` `curl -fsSL https://kubeblocks.io/installer/install_cli.sh | bash -s v1.0.1` Your system is linux_amd64 Installing kbcli ... Downloading ... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 59 33.6M 59 20.0M 0 0 105M 0 --:--:-- --:--:-- --:--:-- 105M 100 33.6M 100 33.6M 0 0 153M 0 --:--:-- --:--:-- --:--:-- 485M kbcli installed successfully. Kubernetes: v1.32.6 KubeBlocks: 1.0.1 kbcli: 1.0.1 Make sure your docker service is running and begin your journey with kbcli: kbcli playground init For more information on how to get started, please visit: https://kubeblocks.io download kbcli v1.0.1 done Kubernetes: v1.32.6 KubeBlocks: 1.0.1 kbcli: 1.0.1 Kubernetes Env: v1.32.6 check snapshot controller check snapshot controller done POD_RESOURCES: aks kb-default-sc found aks default-vsc found found default storage class: default KubeBlocks version is:1.0.1 skip upgrade KubeBlocks current KubeBlocks version: 1.0.1 Error: no repositories to show helm repo add chaos-mesh https://charts.chaos-mesh.org "chaos-mesh" has been added to your repositories add helm chart repo chaos-mesh success chaos mesh already installed check component definition set component name:vastbase set component version set component version:vastbase set service versions:2.2.15 set service versions sorted:2.2.15 set vastbase component definition set vastbase component definition vastbase-2.2-1.0.1 REPORT_COUNT 0:0 set replicas first:3,2.2.15 set replicas third:3,2.2.15 set replicas fourth:3,2.2.15 set minimum cmpv service version set minimum cmpv service version replicas:3,2.2.15 REPORT_COUNT:1 CLUSTER_TOPOLOGY: set vastbase component definition set vastbase component definition vastbase-2.2-1.0.1 LIMIT_CPU:0.5 LIMIT_MEMORY:2 storage size: 20 CLUSTER_NAME:vastbase-rqfsww No resources found in ns-zklqi namespace. pod_info: termination_policy:WipeOut create 3 replica WipeOut vastbase cluster check component definition set component definition by component version check cmpd by labels set component definition1: vastbase-2.2-1.0.1 by component version:vastbase apiVersion: v1 kind: Secret metadata: name: vastbase-rqfsww-license namespace: ns-zklqi type: Opaque data: --- apiVersion: apps.kubeblocks.io/v1 kind: Cluster metadata: name: vastbase-rqfsww namespace: ns-zklqi annotations: kubeblocks.io/host-network: "vastbase" spec: clusterDef: vastbase topology: terminationPolicy: WipeOut componentSpecs: - name: vastbase serviceVersion: 2.2.15 schedulingPolicy: affinity: podAntiAffinity: requiredDuringSchedulingIgnoredDuringExecution: - labelSelector: matchLabels: app.kubernetes.io/instance: vastbase-rqfsww apps.kubeblocks.io/component-name: vastbase topologyKey: kubernetes.io/hostname replicas: 3 disableExporter: true resources: requests: cpu: 500m memory: 2Gi limits: cpu: 500m memory: 2Gi volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi volumes: - name: license secret: secretName: vastbase-rqfsww-license `kubectl apply -f test_create_vastbase-rqfsww.yaml` secret/vastbase-rqfsww-license created cluster.apps.kubeblocks.io/vastbase-rqfsww created apply test_create_vastbase-rqfsww.yaml Success `rm -rf test_create_vastbase-rqfsww.yaml` check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Creating Sep 11,2025 17:22 UTC+0800 clusterdefinition.kubeblocks.io/name=vastbase 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:Failed cluster_status:Failed check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:22 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:23 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:24 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check cluster connect done `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check pod vastbase-rqfsww-vastbase-2 container_name vastbase exist password c7a1hn01L5FB996N Container vastbase logs contain secret password:+ vb_initdb -D /var/lib/vastbase/dn --nodename vastbase_rqfsww_vastbase_2 -w c7a1hn01L5FB996N --dbcompatibility=PG + execute_sql 'create user IF NOT EXISTS root sysadmin monadmin ENCRYPTED PASSWORD '\''c7a1hn01L5FB996N'\''' + echo 'Execute SQL: vsql postgres://%2Ftmp:5432 -v ON_ERROR_STOP=1 -c "create user IF NOT EXISTS root sysadmin monadmin ENCRYPTED PASSWORD '\''c7a1hn01L5FB996N'\''"' Execute SQL: vsql postgres://%2Ftmp:5432 -v ON_ERROR_STOP=1 -c "create user IF NOT EXISTS root sysadmin monadmin ENCRYPTED PASSWORD 'c7a1hn01L5FB996N'" + vsql postgres://%2Ftmp:5432 -v ON_ERROR_STOP=1 -c 'create user IF NOT EXISTS root sysadmin monadmin ENCRYPTED PASSWORD '\''c7a1hn01L5FB996N'\''' describe cluster `kbcli cluster describe vastbase-rqfsww --namespace ns-zklqi ` Name: vastbase-rqfsww Created Time: Sep 11,2025 17:22 UTC+0800 NAMESPACE CLUSTER-DEFINITION TOPOLOGY STATUS TERMINATION-POLICY ns-zklqi vastbase replication Running WipeOut Endpoints: COMPONENT INTERNAL EXTERNAL vastbase vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:8999 Topology: COMPONENT SERVICE-VERSION INSTANCE ROLE STATUS AZ NODE CREATED-TIME vastbase 2.2.15 vastbase-rqfsww-vastbase-0 Standby Running 0 aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:22 UTC+0800 vastbase 2.2.15 vastbase-rqfsww-vastbase-1 Standby Running 0 aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:23 UTC+0800 vastbase 2.2.15 vastbase-rqfsww-vastbase-2 Primary Running 0 aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:24 UTC+0800 Resources Allocation: COMPONENT INSTANCE-TEMPLATE CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS vastbase 500m / 500m 2Gi / 2Gi data:20Gi default Images: COMPONENT COMPONENT-DEFINITION IMAGE vastbase vastbase-2.2-1.0.1 docker.io/apecloud/vastbase:0.0.20 Data Protection: BACKUP-REPO AUTO-BACKUP BACKUP-SCHEDULE BACKUP-METHOD BACKUP-RETENTION RECOVERABLE-TIME Show cluster events: kbcli cluster list-events -n ns-zklqi vastbase-rqfsww `kbcli cluster label vastbase-rqfsww app.kubernetes.io/instance- --namespace ns-zklqi ` label "app.kubernetes.io/instance" not found. `kbcli cluster label vastbase-rqfsww app.kubernetes.io/instance=vastbase-rqfsww --namespace ns-zklqi ` `kbcli cluster label vastbase-rqfsww --list --namespace ns-zklqi ` NAME NAMESPACE LABELS vastbase-rqfsww ns-zklqi app.kubernetes.io/instance=vastbase-rqfsww clusterdefinition.kubeblocks.io/name=vastbase label cluster app.kubernetes.io/instance=vastbase-rqfsww Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=vastbase-rqfsww --namespace ns-zklqi ` `kbcli cluster label vastbase-rqfsww --list --namespace ns-zklqi ` NAME NAMESPACE LABELS vastbase-rqfsww ns-zklqi app.kubernetes.io/instance=vastbase-rqfsww case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=vastbase label cluster case.name=kbcli.test1 Success `kbcli cluster label vastbase-rqfsww case.name=kbcli.test2 --overwrite --namespace ns-zklqi ` `kbcli cluster label vastbase-rqfsww --list --namespace ns-zklqi ` NAME NAMESPACE LABELS vastbase-rqfsww ns-zklqi app.kubernetes.io/instance=vastbase-rqfsww case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=vastbase label cluster case.name=kbcli.test2 Success `kbcli cluster label vastbase-rqfsww case.name- --namespace ns-zklqi ` `kbcli cluster label vastbase-rqfsww --list --namespace ns-zklqi ` NAME NAMESPACE LABELS vastbase-rqfsww ns-zklqi app.kubernetes.io/instance=vastbase-rqfsww clusterdefinition.kubeblocks.io/name=vastbase delete cluster label case.name Success cluster connect `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"show max_connections;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash ` Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file max_connections ----------------- 200 (1 row) connect cluster Success set max_connections to 200 insert batch data by db client Error from server (NotFound): pods "test-db-client-executionloop-vastbase-rqfsww" not found `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-executionloop-vastbase-rqfsww --namespace ns-zklqi ` Error from server (NotFound): pods "test-db-client-executionloop-vastbase-rqfsww" not found 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. Error from server (NotFound): pods "test-db-client-executionloop-vastbase-rqfsww" not found `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres apiVersion: v1 kind: Pod metadata: name: test-db-client-executionloop-vastbase-rqfsww namespace: ns-zklqi spec: containers: - name: test-dbclient imagePullPolicy: IfNotPresent image: docker.io/apecloud/dbclient:test args: - "--host" - "vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local" - "--user" - "root" - "--password" - "c7a1hn01L5FB996N" - "--port" - "5432" - "--dbtype" - "vastbase" - "--test" - "executionloop" - "--duration" - "60" - "--interval" - "1" restartPolicy: Never `kubectl apply -f test-db-client-executionloop-vastbase-rqfsww.yaml` pod/test-db-client-executionloop-vastbase-rqfsww created apply test-db-client-executionloop-vastbase-rqfsww.yaml Success `rm -rf test-db-client-executionloop-vastbase-rqfsww.yaml` check pod status pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 0/1 ContainerCreating 0 5s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 9s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 14s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 19s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 25s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 30s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 35s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 40s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 45s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 50s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 55s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 60s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 1/1 Running 0 66s check pod test-db-client-executionloop-vastbase-rqfsww status done pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-vastbase-rqfsww 0/1 Completed 0 71s check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:22 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:23 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:24 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check cluster connect done SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider] Sep 11, 2025 9:29:56 AM com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [1ebdb931-917d-4199-b11f-e69732ab6771] Try to connect. IP: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 Sep 11, 2025 9:29:56 AM com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [10.244.5.36:42956/astbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local/10.0.8.61:5432] Connection is established. ID: 1ebdb931-917d-4199-b11f-e69732ab6771 Sep 11, 2025 9:29:56 AM com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: Connect complete. ID: 1ebdb931-917d-4199-b11f-e69732ab6771 Execution loop start: create databases executions_loop CREATE DATABASE executions_loop; reconnect connection executions_loop Sep 11, 2025 9:29:59 AM com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [2682c067-792c-4797-b163-401c0636f17d] Try to connect. IP: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 Sep 11, 2025 9:29:59 AM com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [10.244.5.36:42958/astbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local/10.0.8.61:5432] Connection is established. ID: 2682c067-792c-4797-b163-401c0636f17d Sep 11, 2025 9:29:59 AM com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: Connect complete. ID: 2682c067-792c-4797-b163-401c0636f17d drop table executions_loop_table DROP TABLE IF EXISTS executions_loop_table; create table executions_loop_table CREATE TABLE IF NOT EXISTS executions_loop_table (id SERIAL PRIMARY KEY , value text); Execution loop start:INSERT INTO executions_loop_table (value) VALUES ('executions_loop_test_1'); [ 1s ] executions total: 1 successful: 1 failed: 0 disconnect: 0 [ 2s ] executions total: 86 successful: 86 failed: 0 disconnect: 0 [ 3s ] executions total: 205 successful: 205 failed: 0 disconnect: 0 [ 4s ] executions total: 351 successful: 351 failed: 0 disconnect: 0 [ 5s ] executions total: 502 successful: 502 failed: 0 disconnect: 0 [ 6s ] executions total: 606 successful: 606 failed: 0 disconnect: 0 [ 7s ] executions total: 793 successful: 793 failed: 0 disconnect: 0 [ 8s ] executions total: 995 successful: 995 failed: 0 disconnect: 0 [ 9s ] executions total: 1180 successful: 1180 failed: 0 disconnect: 0 [ 10s ] executions total: 1308 successful: 1308 failed: 0 disconnect: 0 [ 11s ] executions total: 1500 successful: 1500 failed: 0 disconnect: 0 [ 12s ] executions total: 1681 successful: 1681 failed: 0 disconnect: 0 [ 13s ] executions total: 1873 successful: 1873 failed: 0 disconnect: 0 [ 14s ] executions total: 2038 successful: 2038 failed: 0 disconnect: 0 [ 15s ] executions total: 2205 successful: 2205 failed: 0 disconnect: 0 [ 16s ] executions total: 2405 successful: 2405 failed: 0 disconnect: 0 [ 17s ] executions total: 2593 successful: 2593 failed: 0 disconnect: 0 [ 18s ] executions total: 2786 successful: 2786 failed: 0 disconnect: 0 [ 19s ] executions total: 2987 successful: 2987 failed: 0 disconnect: 0 [ 20s ] executions total: 3195 successful: 3195 failed: 0 disconnect: 0 [ 21s ] executions total: 3378 successful: 3378 failed: 0 disconnect: 0 [ 22s ] executions total: 3575 successful: 3575 failed: 0 disconnect: 0 [ 23s ] executions total: 3768 successful: 3768 failed: 0 disconnect: 0 [ 24s ] executions total: 3937 successful: 3937 failed: 0 disconnect: 0 [ 25s ] executions total: 4137 successful: 4137 failed: 0 disconnect: 0 [ 26s ] executions total: 4345 successful: 4345 failed: 0 disconnect: 0 [ 27s ] executions total: 4514 successful: 4514 failed: 0 disconnect: 0 [ 28s ] executions total: 4722 successful: 4722 failed: 0 disconnect: 0 [ 29s ] executions total: 4923 successful: 4923 failed: 0 disconnect: 0 [ 30s ] executions total: 5098 successful: 5098 failed: 0 disconnect: 0 [ 31s ] executions total: 5301 successful: 5301 failed: 0 disconnect: 0 [ 32s ] executions total: 5496 successful: 5496 failed: 0 disconnect: 0 [ 33s ] executions total: 5687 successful: 5687 failed: 0 disconnect: 0 [ 34s ] executions total: 5874 successful: 5874 failed: 0 disconnect: 0 [ 35s ] executions total: 6076 successful: 6076 failed: 0 disconnect: 0 [ 36s ] executions total: 6246 successful: 6246 failed: 0 disconnect: 0 [ 37s ] executions total: 6449 successful: 6449 failed: 0 disconnect: 0 [ 38s ] executions total: 6640 successful: 6640 failed: 0 disconnect: 0 [ 39s ] executions total: 6799 successful: 6799 failed: 0 disconnect: 0 [ 40s ] executions total: 6994 successful: 6994 failed: 0 disconnect: 0 [ 41s ] executions total: 7194 successful: 7194 failed: 0 disconnect: 0 [ 42s ] executions total: 7355 successful: 7355 failed: 0 disconnect: 0 [ 43s ] executions total: 7547 successful: 7547 failed: 0 disconnect: 0 [ 44s ] executions total: 7723 successful: 7723 failed: 0 disconnect: 0 [ 45s ] executions total: 7872 successful: 7872 failed: 0 disconnect: 0 [ 46s ] executions total: 8027 successful: 8027 failed: 0 disconnect: 0 [ 47s ] executions total: 8191 successful: 8191 failed: 0 disconnect: 0 [ 48s ] executions total: 8352 successful: 8352 failed: 0 disconnect: 0 [ 49s ] executions total: 8505 successful: 8505 failed: 0 disconnect: 0 [ 50s ] executions total: 8673 successful: 8673 failed: 0 disconnect: 0 [ 51s ] executions total: 8814 successful: 8814 failed: 0 disconnect: 0 [ 52s ] executions total: 8987 successful: 8987 failed: 0 disconnect: 0 [ 53s ] executions total: 9164 successful: 9164 failed: 0 disconnect: 0 [ 54s ] executions total: 9329 successful: 9329 failed: 0 disconnect: 0 [ 55s ] executions total: 9479 successful: 9479 failed: 0 disconnect: 0 [ 56s ] executions total: 9666 successful: 9666 failed: 0 disconnect: 0 [ 57s ] executions total: 9837 successful: 9837 failed: 0 disconnect: 0 [ 58s ] executions total: 9988 successful: 9988 failed: 0 disconnect: 0 [ 60s ] executions total: 10033 successful: 10033 failed: 0 disconnect: 0 Test Result: Total Executions: 10033 Successful Executions: 10033 Failed Executions: 0 Disconnection Counts: 0 Connection Information: Database Type: vastbase Host: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local Port: 5432 Database: Table: User: root Org: Access Mode: mysql Test Type: executionloop Query: Duration: 60 seconds Interval: 1 seconds DB_CLIENT_BATCH_DATA_COUNT: 10033 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-executionloop-vastbase-rqfsww --namespace ns-zklqi ` pod/test-db-client-executionloop-vastbase-rqfsww patched (no change) 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 "test-db-client-executionloop-vastbase-rqfsww" force deleted `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"DROP TABLE IF EXISTS tmp_table; CREATE TABLE IF NOT EXISTS tmp_table (id INT PRIMARY KEY , value text); INSERT INTO tmp_table (id,value) VALUES (1,'gzrea');\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file NOTICE: table "tmp_table" does not exist, skipping DROP TABLE NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "tmp_table_pkey" for table "tmp_table" CREATE TABLE INSERT 0 1 add consistent data gzrea Success LB_TYPE is set to: intranet cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose vastbase-rqfsww --auto-approve --force=true --type intranet --enable true --components vastbase --role-selector Primary --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-expose-pr2dn created successfully, you can view the progress: kbcli cluster describe-ops vastbase-rqfsww-expose-pr2dn -n ns-zklqi check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww Creating -/- Sep 11,2025 17:31 UTC+0800 check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:22 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:23 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:24 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check cluster connect done check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 17:31 UTC+0800 check ops status done ops_status:vastbase-rqfsww-expose-pr2dn ns-zklqi Expose vastbase-rqfsww vastbase Succeed 1/1 Sep 11,2025 17:31 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vastbase-rqfsww-expose-pr2dn --namespace ns-zklqi ` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-expose-pr2dn patched `kbcli cluster delete-ops --name vastbase-rqfsww-expose-pr2dn --force --auto-approve --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-expose-pr2dn deleted `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check db_client batch data Success test failover dnserror check cluster status before cluster-failover-dnserror check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnserror-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): dnschaos.chaos-mesh.org "test-chaos-mesh-dnserror-vastbase-rqfsww" not found Error from server (NotFound): dnschaos.chaos-mesh.org "test-chaos-mesh-dnserror-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: DNSChaos metadata: name: test-chaos-mesh-dnserror-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-2 mode: all action: error duration: 2m `kubectl apply -f test-chaos-mesh-dnserror-vastbase-rqfsww.yaml` dnschaos.chaos-mesh.org/test-chaos-mesh-dnserror-vastbase-rqfsww created apply test-chaos-mesh-dnserror-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-dnserror-vastbase-rqfsww.yaml` dnserror chaos test waiting 120 seconds check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:22 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:23 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:20Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:24 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnserror-vastbase-rqfsww --namespace ns-zklqi ` 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. dnschaos.chaos-mesh.org "test-chaos-mesh-dnserror-vastbase-rqfsww" force deleted dnschaos.chaos-mesh.org/test-chaos-mesh-dnserror-vastbase-rqfsww patched check failover pod name failover pod name:vastbase-rqfsww-vastbase-2 failover dnserror Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check db_client batch data Success `kubectl get pvc -l app.kubernetes.io/instance=vastbase-rqfsww,apps.kubeblocks.io/component-name=vastbase,apps.kubeblocks.io/vct-name=data --namespace ns-zklqi ` cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in vastbase-rqfsww namespace. `kbcli cluster volume-expand vastbase-rqfsww --auto-approve --force=true --components vastbase --volume-claim-templates data --storage 25Gi --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-volumeexpansion-tzgt2 created successfully, you can view the progress: kbcli cluster describe-ops vastbase-rqfsww-volumeexpansion-tzgt2 -n ns-zklqi check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-volumeexpansion-tzgt2 ns-zklqi VolumeExpansion vastbase-rqfsww vastbase Creating -/- Sep 11,2025 17:35 UTC+0800 check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Updating Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase 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 vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:22 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:23 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:24 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check cluster connect done No resources found in vastbase-rqfsww namespace. check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-volumeexpansion-tzgt2 ns-zklqi VolumeExpansion vastbase-rqfsww vastbase Succeed 3/3 Sep 11,2025 17:35 UTC+0800 check ops status done ops_status:vastbase-rqfsww-volumeexpansion-tzgt2 ns-zklqi VolumeExpansion vastbase-rqfsww vastbase Succeed 3/3 Sep 11,2025 17:35 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vastbase-rqfsww-volumeexpansion-tzgt2 --namespace ns-zklqi ` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-volumeexpansion-tzgt2 patched `kbcli cluster delete-ops --name vastbase-rqfsww-volumeexpansion-tzgt2 --force --auto-approve --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-volumeexpansion-tzgt2 deleted `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check db_client batch data Success test failover networkpartition check cluster status before cluster-failover-networkpartition check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkpartition-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkpartition-vastbase-rqfsww" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkpartition-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkpartition-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-2 action: partition mode: all target: mode: all selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-0 direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkpartition-vastbase-rqfsww.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkpartition-vastbase-rqfsww created apply test-chaos-mesh-networkpartition-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-networkpartition-vastbase-rqfsww.yaml` networkpartition chaos test waiting 120 seconds check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:22 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:23 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:24 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkpartition-vastbase-rqfsww --namespace ns-zklqi ` 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. networkchaos.chaos-mesh.org "test-chaos-mesh-networkpartition-vastbase-rqfsww" force deleted networkchaos.chaos-mesh.org/test-chaos-mesh-networkpartition-vastbase-rqfsww patched check failover pod name failover pod name:vastbase-rqfsww-vastbase-2 failover networkpartition Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-2 --namespace ns-zklqi -- bash` check db_client batch data Success test failover networklossover check cluster status before cluster-failover-networklossover check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networklossover-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networklossover-vastbase-rqfsww" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networklossover-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networklossover-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-2 mode: all action: loss loss: loss: '100' correlation: '100' direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networklossover-vastbase-rqfsww.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networklossover-vastbase-rqfsww created apply test-chaos-mesh-networklossover-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-networklossover-vastbase-rqfsww.yaml` networklossover chaos test waiting 120 seconds check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:22 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:23 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:24 UTC+0800 check pod status done check cluster role Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2;Standby: vastbase-rqfsww-vastbase-1 check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networklossover-vastbase-rqfsww --namespace ns-zklqi ` 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. networkchaos.chaos-mesh.org "test-chaos-mesh-networklossover-vastbase-rqfsww" force deleted Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networklossover-vastbase-rqfsww" not found check failover pod name failover pod name:vastbase-rqfsww-vastbase-0 failover networklossover Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check db_client batch data Success test failover podkill check cluster status before cluster-failover-podkill check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge PodChaos test-chaos-mesh-podkill-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podkill-vastbase-rqfsww" not found Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podkill-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: PodChaos metadata: name: test-chaos-mesh-podkill-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-0 mode: all action: pod-kill `kubectl apply -f test-chaos-mesh-podkill-vastbase-rqfsww.yaml` podchaos.chaos-mesh.org/test-chaos-mesh-podkill-vastbase-rqfsww created apply test-chaos-mesh-podkill-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-podkill-vastbase-rqfsww.yaml` check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Updating Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase 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 vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:47 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:23 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:24 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge PodChaos test-chaos-mesh-podkill-vastbase-rqfsww --namespace ns-zklqi ` 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. podchaos.chaos-mesh.org "test-chaos-mesh-podkill-vastbase-rqfsww" force deleted podchaos.chaos-mesh.org/test-chaos-mesh-podkill-vastbase-rqfsww patched check failover pod name failover pod name:vastbase-rqfsww-vastbase-1 failover podkill Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check db_client batch data Success cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop vastbase-rqfsww --auto-approve --force=true --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-stop-q9qf7 created successfully, you can view the progress: kbcli cluster describe-ops vastbase-rqfsww-stop-q9qf7 -n ns-zklqi check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-stop-q9qf7 ns-zklqi Stop vastbase-rqfsww vastbase Running 0/3 Sep 11,2025 17:48 UTC+0800 check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Stopping Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase 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 vastbase-rqfsww --namespace ns-zklqi ` 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 vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-stop-q9qf7 ns-zklqi Stop vastbase-rqfsww vastbase Succeed 3/3 Sep 11,2025 17:48 UTC+0800 check ops status done ops_status:vastbase-rqfsww-stop-q9qf7 ns-zklqi Stop vastbase-rqfsww vastbase Succeed 3/3 Sep 11,2025 17:48 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vastbase-rqfsww-stop-q9qf7 --namespace ns-zklqi ` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-stop-q9qf7 patched `kbcli cluster delete-ops --name vastbase-rqfsww-stop-q9qf7 --force --auto-approve --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-stop-q9qf7 deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start vastbase-rqfsww --force=true --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-start-v5kcx created successfully, you can view the progress: kbcli cluster describe-ops vastbase-rqfsww-start-v5kcx -n ns-zklqi check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-start-v5kcx ns-zklqi Start vastbase-rqfsww Creating -/- Sep 11,2025 17:49 UTC+0800 check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Updating Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase 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 vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check cluster connect done check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-start-v5kcx ns-zklqi Start vastbase-rqfsww vastbase Succeed 3/3 Sep 11,2025 17:49 UTC+0800 check ops status done ops_status:vastbase-rqfsww-start-v5kcx ns-zklqi Start vastbase-rqfsww vastbase Succeed 3/3 Sep 11,2025 17:49 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vastbase-rqfsww-start-v5kcx --namespace ns-zklqi ` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-start-v5kcx patched `kbcli cluster delete-ops --name vastbase-rqfsww-start-v5kcx --force --auto-approve --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-start-v5kcx deleted `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check db_client batch data Success test failover networkduplicate check cluster status before cluster-failover-networkduplicate check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkduplicate-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkduplicate-vastbase-rqfsww" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkduplicate-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkduplicate-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-1 mode: all action: duplicate duplicate: duplicate: '100' correlation: '100' direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkduplicate-vastbase-rqfsww.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkduplicate-vastbase-rqfsww created apply test-chaos-mesh-networkduplicate-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-networkduplicate-vastbase-rqfsww.yaml` networkduplicate chaos test waiting 120 seconds check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkduplicate-vastbase-rqfsww --namespace ns-zklqi ` 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. networkchaos.chaos-mesh.org "test-chaos-mesh-networkduplicate-vastbase-rqfsww" force deleted Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkduplicate-vastbase-rqfsww" not found check failover pod name failover pod name:vastbase-rqfsww-vastbase-1 failover networkduplicate Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check db_client batch data Success test failover oom check cluster status before cluster-failover-oom check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-oom-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-oom-vastbase-rqfsww" not found Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-oom-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: StressChaos metadata: name: test-chaos-mesh-oom-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-1 mode: all stressors: memory: workers: 1 size: "100GB" oomScoreAdj: -1000 duration: 2m `kubectl apply -f test-chaos-mesh-oom-vastbase-rqfsww.yaml` stresschaos.chaos-mesh.org/test-chaos-mesh-oom-vastbase-rqfsww created apply test-chaos-mesh-oom-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-oom-vastbase-rqfsww.yaml` check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 check pod status done check cluster role Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-oom-vastbase-rqfsww --namespace ns-zklqi ` 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. stresschaos.chaos-mesh.org "test-chaos-mesh-oom-vastbase-rqfsww" force deleted stresschaos.chaos-mesh.org/test-chaos-mesh-oom-vastbase-rqfsww patched check failover pod name failover pod name:vastbase-rqfsww-vastbase-0 failover oom Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check db_client batch data Success test switchover cluster promote check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster promote vastbase-rqfsww --auto-approve --force=true --instance vastbase-rqfsww-vastbase-0 --candidate vastbase-rqfsww-vastbase-1 --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-switchover-n2ts5 created successfully, you can view the progress: kbcli cluster describe-ops vastbase-rqfsww-switchover-n2ts5 -n ns-zklqi check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww Creating -/- Sep 11,2025 18:00 UTC+0800 check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww vastbase-rqfsww-vastbase Running 0/1 Sep 11,2025 18:00 UTC+0800 ops_status:vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww vastbase-rqfsww-vastbase Running 0/1 Sep 11,2025 18:00 UTC+0800 ops_status:vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww vastbase-rqfsww-vastbase Running 0/1 Sep 11,2025 18:00 UTC+0800 ops_status:vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww vastbase-rqfsww-vastbase Running 0/1 Sep 11,2025 18:00 UTC+0800 ops_status:vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww vastbase-rqfsww-vastbase Running 0/1 Sep 11,2025 18:00 UTC+0800 ops_status:vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww vastbase-rqfsww-vastbase Running 0/1 Sep 11,2025 18:00 UTC+0800 ops_status:vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww vastbase-rqfsww-vastbase Running 0/1 Sep 11,2025 18:00 UTC+0800 ops_status:vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww vastbase-rqfsww-vastbase Running 0/1 Sep 11,2025 18:00 UTC+0800 ops_status:vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww vastbase-rqfsww-vastbase Running 0/1 Sep 11,2025 18:00 UTC+0800 ops_status:vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww vastbase-rqfsww-vastbase Running 0/1 Sep 11,2025 18:00 UTC+0800 check ops status done ops_status:vastbase-rqfsww-switchover-n2ts5 ns-zklqi Switchover vastbase-rqfsww vastbase-rqfsww-vastbase Succeed 1/1 Sep 11,2025 18:00 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vastbase-rqfsww-switchover-n2ts5 --namespace ns-zklqi ` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-switchover-n2ts5 patched `kbcli cluster delete-ops --name vastbase-rqfsww-switchover-n2ts5 --force --auto-approve --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-switchover-n2ts5 deleted `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check db_client batch data Success switchover pod:vastbase-rqfsww-vastbase-1 switchover success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres apiVersion: v1 kind: Pod metadata: name: benchtest-vastbase-rqfsww namespace: ns-zklqi spec: containers: - name: test-sysbench imagePullPolicy: IfNotPresent image: docker.io/apecloud/customsuites:latest env: - name: TYPE value: "2" - name: FLAG value: "0" - name: CONFIGS value: "mode:all,driver:pgsql,host:vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local,user:root,password:c7a1hn01L5FB996N,port:5432,db:benchtest,tables:5,threads:4,times:10,size:1000,type:oltp_read_write" restartPolicy: Never `kubectl apply -f benchtest-vastbase-rqfsww.yaml` pod/benchtest-vastbase-rqfsww created apply benchtest-vastbase-rqfsww.yaml Success check pod status pod_status:NAME READY STATUS RESTARTS AGE benchtest-vastbase-rqfsww 0/1 ContainerCreating 0 0s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vastbase-rqfsww 1/1 Running 0 4s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vastbase-rqfsww 1/1 Running 0 9s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vastbase-rqfsww 1/1 Running 0 15s check pod benchtest-vastbase-rqfsww status done pod_status:NAME READY STATUS RESTARTS AGE benchtest-vastbase-rqfsww 0/1 Completed 0 20s `rm -rf benchtest-vastbase-rqfsww.yaml` `kubectl logs benchtest-vastbase-rqfsww --tail 30 --namespace ns-zklqi ` [ 7s ] thds: 4 tps: 63.00 qps: 1293.06 (r/w/o: 905.04/261.01/127.01) lat (ms,99%): 102.97 err/s: 0.00 reconn/s: 0.00 [ 8s ] thds: 4 tps: 73.00 qps: 1436.95 (r/w/o: 1006.97/283.99/146.00) lat (ms,99%): 99.33 err/s: 0.00 reconn/s: 0.00 [ 9s ] thds: 4 tps: 73.00 qps: 1454.04 (r/w/o: 1017.03/291.01/146.00) lat (ms,99%): 95.81 err/s: 0.00 reconn/s: 0.00 [ 10s ] thds: 4 tps: 71.00 qps: 1431.07 (r/w/o: 1000.05/286.01/145.01) lat (ms,99%): 104.84 err/s: 0.00 reconn/s: 0.00 SQL statistics: queries performed: read: 10374 write: 2955 other: 1489 total: 14818 transactions: 740 (73.92 per sec.) queries: 14818 (1480.17 per sec.) ignored errors: 1 (0.10 per sec.) reconnects: 0 (0.00 per sec.) General statistics: total time: 10.0096s total number of events: 740 Latency (ms): min: 8.52 avg: 54.08 max: 205.88 99th percentile: 106.75 sum: 40016.50 Threads fairness: events (avg/stddev): 185.0000/3.67 execution time (avg/stddev): 10.0041/0.00 `kubectl delete pod benchtest-vastbase-rqfsww --force --namespace ns-zklqi ` 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 "benchtest-vastbase-rqfsww" force deleted LB_TYPE is set to: intranet No resources found in ns-zklqi namespace. `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres apiVersion: v1 kind: Pod metadata: name: benchtest-vastbase-rqfsww namespace: ns-zklqi spec: containers: - name: test-sysbench imagePullPolicy: IfNotPresent image: docker.io/apecloud/customsuites:latest env: - name: TYPE value: "2" - name: FLAG value: "0" - name: CONFIGS value: "mode:all,driver:pgsql,host:10.224.0.8,user:root,password:c7a1hn01L5FB996N,port:5432,db:benchtest,tables:5,threads:4,times:10,size:1000,type:oltp_read_write" restartPolicy: Never `kubectl apply -f benchtest-vastbase-rqfsww.yaml` pod/benchtest-vastbase-rqfsww created apply benchtest-vastbase-rqfsww.yaml Success check pod status pod_status:NAME READY STATUS RESTARTS AGE benchtest-vastbase-rqfsww 0/1 ContainerCreating 0 0s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vastbase-rqfsww 1/1 Running 0 4s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vastbase-rqfsww 1/1 Running 0 9s check pod benchtest-vastbase-rqfsww status done pod_status:NAME READY STATUS RESTARTS AGE benchtest-vastbase-rqfsww 0/1 Completed 0 14s `rm -rf benchtest-vastbase-rqfsww.yaml` `kubectl logs benchtest-vastbase-rqfsww --tail 30 --namespace ns-zklqi ` [ 7s ] thds: 4 tps: 81.00 qps: 1606.03 (r/w/o: 1128.02/316.01/162.00) lat (ms,99%): 95.81 err/s: 0.00 reconn/s: 0.00 [ 8s ] thds: 4 tps: 40.00 qps: 810.09 (r/w/o: 568.06/162.02/80.01) lat (ms,99%): 95.81 err/s: 0.00 reconn/s: 0.00 [ 9s ] thds: 4 tps: 32.00 qps: 653.95 (r/w/o: 457.97/128.99/67.00) lat (ms,99%): 1109.09 err/s: 2.00 reconn/s: 0.00 [ 10s ] thds: 4 tps: 81.00 qps: 1632.06 (r/w/o: 1141.04/329.01/162.01) lat (ms,99%): 92.42 err/s: 0.00 reconn/s: 0.00 SQL statistics: queries performed: read: 9324 write: 2652 other: 1333 total: 13309 transactions: 661 (65.99 per sec.) queries: 13309 (1328.74 per sec.) ignored errors: 5 (0.50 per sec.) reconnects: 0 (0.00 per sec.) General statistics: total time: 10.0148s total number of events: 661 Latency (ms): min: 8.70 avg: 60.57 max: 1107.10 99th percentile: 110.66 sum: 40035.97 Threads fairness: events (avg/stddev): 165.2500/1.92 execution time (avg/stddev): 10.0090/0.00 `kubectl delete pod benchtest-vastbase-rqfsww --force --namespace ns-zklqi ` 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 "benchtest-vastbase-rqfsww" force deleted test failover networkbandwidth check cluster status before cluster-failover-networkbandwidth check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkbandwidth-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkbandwidth-vastbase-rqfsww" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkbandwidth-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkbandwidth-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-1 action: bandwidth mode: all bandwidth: rate: '1bps' limit: 20971520 buffer: 10000 duration: 2m `kubectl apply -f test-chaos-mesh-networkbandwidth-vastbase-rqfsww.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkbandwidth-vastbase-rqfsww created apply test-chaos-mesh-networkbandwidth-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-networkbandwidth-vastbase-rqfsww.yaml` networkbandwidth chaos test waiting 120 seconds check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 check pod status done check cluster role Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkbandwidth-vastbase-rqfsww --namespace ns-zklqi ` 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. networkchaos.chaos-mesh.org "test-chaos-mesh-networkbandwidth-vastbase-rqfsww" force deleted Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkbandwidth-vastbase-rqfsww" not found check failover pod name failover pod name:vastbase-rqfsww-vastbase-0 failover networkbandwidth Failure `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check db_client batch data Success cluster vastbase scale-out cluster vastbase scale-out replicas: 4 check cluster status before ops check cluster status done cluster_status:Running No resources found in vastbase-rqfsww namespace. `kbcli cluster scale-out vastbase-rqfsww --auto-approve --force=true --components vastbase --replicas 1 --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-horizontalscaling-sg6tv created successfully, you can view the progress: kbcli cluster describe-ops vastbase-rqfsww-horizontalscaling-sg6tv -n ns-zklqi check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-horizontalscaling-sg6tv ns-zklqi HorizontalScaling vastbase-rqfsww vastbase Creating -/- Sep 11,2025 18:07 UTC+0800 check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Updating Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase 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 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 vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-3 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000005/10.224.0.10 Sep 11,2025 18:07 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 vastbase-rqfsww-vastbase-3 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done No resources found in vastbase-rqfsww namespace. check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-horizontalscaling-sg6tv ns-zklqi HorizontalScaling vastbase-rqfsww vastbase Succeed 1/1 Sep 11,2025 18:07 UTC+0800 check ops status done ops_status:vastbase-rqfsww-horizontalscaling-sg6tv ns-zklqi HorizontalScaling vastbase-rqfsww vastbase Succeed 1/1 Sep 11,2025 18:07 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vastbase-rqfsww-horizontalscaling-sg6tv --namespace ns-zklqi ` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-horizontalscaling-sg6tv patched `kbcli cluster delete-ops --name vastbase-rqfsww-horizontalscaling-sg6tv --force --auto-approve --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-horizontalscaling-sg6tv deleted `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check db_client batch data Success cluster vastbase scale-in cluster vastbase scale-in replicas: 3 check cluster status before ops check cluster status done cluster_status:Running No resources found in vastbase-rqfsww namespace. `kbcli cluster scale-in vastbase-rqfsww --auto-approve --force=true --components vastbase --replicas 1 --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-horizontalscaling-x9cmz created successfully, you can view the progress: kbcli cluster describe-ops vastbase-rqfsww-horizontalscaling-x9cmz -n ns-zklqi check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-horizontalscaling-x9cmz ns-zklqi HorizontalScaling vastbase-rqfsww vastbase Creating -/- Sep 11,2025 18:13 UTC+0800 check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Updating Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done No resources found in vastbase-rqfsww namespace. check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-horizontalscaling-x9cmz ns-zklqi HorizontalScaling vastbase-rqfsww vastbase Succeed 1/1 Sep 11,2025 18:13 UTC+0800 check ops status done ops_status:vastbase-rqfsww-horizontalscaling-x9cmz ns-zklqi HorizontalScaling vastbase-rqfsww vastbase Succeed 1/1 Sep 11,2025 18:13 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vastbase-rqfsww-horizontalscaling-x9cmz --namespace ns-zklqi ` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-horizontalscaling-x9cmz patched `kbcli cluster delete-ops --name vastbase-rqfsww-horizontalscaling-x9cmz --force --auto-approve --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-horizontalscaling-x9cmz deleted `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check db_client batch data Success test failover podfailure check cluster status before cluster-failover-podfailure check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge PodChaos test-chaos-mesh-podfailure-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podfailure-vastbase-rqfsww" not found Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podfailure-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: PodChaos metadata: name: test-chaos-mesh-podfailure-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-0 mode: all action: pod-failure duration: 2m `kubectl apply -f test-chaos-mesh-podfailure-vastbase-rqfsww.yaml` podchaos.chaos-mesh.org/test-chaos-mesh-podfailure-vastbase-rqfsww created apply test-chaos-mesh-podfailure-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-podfailure-vastbase-rqfsww.yaml` podfailure chaos test waiting 120 seconds check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Failed Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase cluster_status:Failed 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 vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge PodChaos test-chaos-mesh-podfailure-vastbase-rqfsww --namespace ns-zklqi ` 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. podchaos.chaos-mesh.org "test-chaos-mesh-podfailure-vastbase-rqfsww" force deleted Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podfailure-vastbase-rqfsww" not found check failover pod name failover pod name:vastbase-rqfsww-vastbase-1 failover podfailure Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check db_client batch data Success cluster configure component_tmp: vastbase apiVersion: operations.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: vastbase-rqfsww-reconfiguring- namespace: ns-zklqi spec: type: Reconfiguring clusterName: vastbase-rqfsww force: true reconfigures: - componentName: vastbase parameters: - key: audit_buffer_fflush_interval value: '150' check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_vastbase-rqfsww.yaml` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-reconfiguring-hxn26 created create test_ops_cluster_vastbase-rqfsww.yaml Success `rm -rf test_ops_cluster_vastbase-rqfsww.yaml` check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-reconfiguring-hxn26 ns-zklqi Reconfiguring vastbase-rqfsww vastbase,vastbase Running -/- Sep 11,2025 18:17 UTC+0800 check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check cluster connect done check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-reconfiguring-hxn26 ns-zklqi Reconfiguring vastbase-rqfsww vastbase,vastbase Succeed -/- Sep 11,2025 18:17 UTC+0800 check ops status done ops_status:vastbase-rqfsww-reconfiguring-hxn26 ns-zklqi Reconfiguring vastbase-rqfsww vastbase,vastbase Succeed -/- Sep 11,2025 18:17 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vastbase-rqfsww-reconfiguring-hxn26 --namespace ns-zklqi ` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-reconfiguring-hxn26 patched `kbcli cluster delete-ops --name vastbase-rqfsww-reconfiguring-hxn26 --force --auto-approve --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-reconfiguring-hxn26 deleted component_config:vastbase check config variables Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file current value_actual: 150s configure:[audit_buffer_fflush_interval] result actual:[150s] equal expected:[150s] `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check db_client batch data Success test failover networkdelay check cluster status before cluster-failover-networkdelay check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkdelay-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkdelay-vastbase-rqfsww" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkdelay-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkdelay-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-1 mode: all action: delay delay: latency: 2000ms correlation: '100' jitter: 0ms direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkdelay-vastbase-rqfsww.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkdelay-vastbase-rqfsww created apply test-chaos-mesh-networkdelay-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-networkdelay-vastbase-rqfsww.yaml` networkdelay chaos test waiting 120 seconds check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkdelay-vastbase-rqfsww --namespace ns-zklqi ` 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. networkchaos.chaos-mesh.org "test-chaos-mesh-networkdelay-vastbase-rqfsww" force deleted networkchaos.chaos-mesh.org/test-chaos-mesh-networkdelay-vastbase-rqfsww patched check failover pod name failover pod name:vastbase-rqfsww-vastbase-1 failover networkdelay Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check db_client batch data Success test failover connectionstress check cluster status before cluster-failover-connectionstress check cluster status done cluster_status:Running Error from server (NotFound): pods "test-db-client-connectionstress-vastbase-rqfsww" not found `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-connectionstress-vastbase-rqfsww --namespace ns-zklqi ` Error from server (NotFound): pods "test-db-client-connectionstress-vastbase-rqfsww" not found 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. Error from server (NotFound): pods "test-db-client-connectionstress-vastbase-rqfsww" not found `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres apiVersion: v1 kind: Pod metadata: name: test-db-client-connectionstress-vastbase-rqfsww namespace: ns-zklqi spec: containers: - name: test-dbclient imagePullPolicy: IfNotPresent image: docker.io/apecloud/dbclient:test args: - "--host" - "vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local" - "--user" - "root" - "--password" - "c7a1hn01L5FB996N" - "--port" - "5432" - "--database" - "postgres" - "--dbtype" - "vastbase" - "--test" - "connectionstress" - "--connections" - "200" - "--duration" - "60" restartPolicy: Never `kubectl apply -f test-db-client-connectionstress-vastbase-rqfsww.yaml` pod/test-db-client-connectionstress-vastbase-rqfsww created apply test-db-client-connectionstress-vastbase-rqfsww.yaml Success `rm -rf test-db-client-connectionstress-vastbase-rqfsww.yaml` check pod status pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-vastbase-rqfsww 1/1 Running 0 5s check pod test-db-client-connectionstress-vastbase-rqfsww status done pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-vastbase-rqfsww 0/1 Completed 0 9s check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check cluster connect done Caused by: java.net.ConnectException: Connection refused (Connection refused) at java.base/java.net.PlainSocketImpl.socketConnect(Native Method) at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.base/java.net.SocksSocketImpl.connect(Unknown Source) at java.base/java.net.Socket.connect(Unknown Source) at com.huawei.opengauss.jdbc.core.PGStream.(PGStream.java:70) at com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:119) at com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:246) ... 11 more Sep 11, 2025 10:19:48 AM com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [93bae589-6c64-44f9-a7ef-a303d40a0f6a] Try to connect. IP: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 Sep 11, 2025 10:19:48 AM org.opengauss.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [bc5ace31-ce68-4c20-9b6f-94d23a059722] Try to connect. IP: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 Failed to connect to Vastbase database: com.huawei.opengauss.jdbc.util.PSQLException: Connection to vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. Trying with database postgres. Sep 11, 2025 10:19:48 AM com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [0ffd0f70-59ff-41b9-87cd-712b0f426bdd] Try to connect. IP: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 Sep 11, 2025 10:19:48 AM org.opengauss.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [b5b80883-0014-4a76-a90d-3f853207fa42] Try to connect. IP: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 java.io.IOException: Failed to connect to Vastbase database: at com.apecloud.dbtester.tester.VastbaseTester.connect(VastbaseTester.java:64) at com.apecloud.dbtester.tester.VastbaseTester.connectionStress(VastbaseTester.java:112) at com.apecloud.dbtester.commons.TestExecutor.executeTest(TestExecutor.java:37) at OneClient.executeTest(OneClient.java:108) at OneClient.main(OneClient.java:40) Caused by: com.huawei.opengauss.jdbc.util.PSQLException: Connection to vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. at com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:370) at com.huawei.opengauss.jdbc.core.ConnectionFactory.openConnection(ConnectionFactory.java:57) at com.huawei.opengauss.jdbc.jdbc.PgConnection.(PgConnection.java:274) at com.huawei.opengauss.jdbc.Driver.makeConnection(Driver.java:576) at com.huawei.opengauss.jdbc.Driver.connect(Driver.java:315) at java.sql/java.sql.DriverManager.getConnection(Unknown Source) at java.sql/java.sql.DriverManager.getConnection(Unknown Source) at com.apecloud.dbtester.tester.VastbaseTester.connect(VastbaseTester.java:62) ... 4 more Caused by: java.net.ConnectException: Connection refused (Connection refused) at java.base/java.net.PlainSocketImpl.socketConnect(Native Method) at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.base/java.net.SocksSocketImpl.connect(Unknown Source) at java.base/java.net.Socket.connect(Unknown Source) at com.huawei.opengauss.jdbc.core.PGStream.(PGStream.java:70) at com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:119) at com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:246) ... 11 more Sep 11, 2025 10:19:48 AM com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [b444e583-f5a4-404b-a963-1526d9ddc1b1] Try to connect. IP: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 Sep 11, 2025 10:19:48 AM org.opengauss.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [e3af606b-64e9-4d0e-a536-0fa8945b9fa3] Try to connect. IP: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 Failed to connect to Vastbase database: com.huawei.opengauss.jdbc.util.PSQLException: Connection to vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. Trying with database postgres. Sep 11, 2025 10:19:48 AM com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [b487ac70-ee35-41ab-9c45-4fc1021d62ae] Try to connect. IP: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 Sep 11, 2025 10:19:48 AM org.opengauss.core.v3.ConnectionFactoryImpl openConnectionImpl INFO: [3a0816d5-45a2-4ae7-8809-873abdbe5bac] Try to connect. IP: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 java.io.IOException: Failed to connect to Vastbase database: at com.apecloud.dbtester.tester.VastbaseTester.connect(VastbaseTester.java:64) at com.apecloud.dbtester.tester.VastbaseTester.connectionStress(VastbaseTester.java:112) at com.apecloud.dbtester.commons.TestExecutor.executeTest(TestExecutor.java:37) at OneClient.executeTest(OneClient.java:108) at OneClient.main(OneClient.java:40) Caused by: com.huawei.opengauss.jdbc.util.PSQLException: Connection to vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections. at com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:370) at com.huawei.opengauss.jdbc.core.ConnectionFactory.openConnection(ConnectionFactory.java:57) at com.huawei.opengauss.jdbc.jdbc.PgConnection.(PgConnection.java:274) at com.huawei.opengauss.jdbc.Driver.makeConnection(Driver.java:576) at com.huawei.opengauss.jdbc.Driver.connect(Driver.java:315) at java.sql/java.sql.DriverManager.getConnection(Unknown Source) at java.sql/java.sql.DriverManager.getConnection(Unknown Source) at com.apecloud.dbtester.tester.VastbaseTester.connect(VastbaseTester.java:62) ... 4 more Caused by: java.net.ConnectException: Connection refused (Connection refused) at java.base/java.net.PlainSocketImpl.socketConnect(Native Method) at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.base/java.net.SocksSocketImpl.connect(Unknown Source) at java.base/java.net.Socket.connect(Unknown Source) at com.huawei.opengauss.jdbc.core.PGStream.(PGStream.java:70) at com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:119) at com.huawei.opengauss.jdbc.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:246) ... 11 more Test Result: null Connection Information: Database Type: vastbase Host: vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local Port: 5432 Database: postgres Table: User: root Org: Access Mode: mysql Test Type: connectionstress Connection Count: 200 Duration: 60 seconds `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-connectionstress-vastbase-rqfsww --namespace ns-zklqi ` pod/test-db-client-connectionstress-vastbase-rqfsww patched (no change) 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 "test-db-client-connectionstress-vastbase-rqfsww" force deleted check failover pod name failover pod name:vastbase-rqfsww-vastbase-1 failover connectionstress Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check db_client batch data Success test failover networkcorruptover check cluster status before cluster-failover-networkcorruptover check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkcorruptover-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkcorruptover-vastbase-rqfsww" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkcorruptover-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkcorruptover-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-1 mode: all action: corrupt corrupt: corrupt: '100' correlation: '100' direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkcorruptover-vastbase-rqfsww.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkcorruptover-vastbase-rqfsww created apply test-chaos-mesh-networkcorruptover-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-networkcorruptover-vastbase-rqfsww.yaml` networkcorruptover chaos test waiting 120 seconds check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 17:49 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 17:52 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 17:52 UTC+0800 check pod status done check cluster role Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 Primary: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-2 check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkcorruptover-vastbase-rqfsww --namespace ns-zklqi ` 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. networkchaos.chaos-mesh.org "test-chaos-mesh-networkcorruptover-vastbase-rqfsww" force deleted networkchaos.chaos-mesh.org/test-chaos-mesh-networkcorruptover-vastbase-rqfsww patched check failover pod name failover pod name:vastbase-rqfsww-vastbase-0 failover networkcorruptover Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check db_client batch data Success cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart vastbase-rqfsww --auto-approve --force=true --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-restart-p8mrt created successfully, you can view the progress: kbcli cluster describe-ops vastbase-rqfsww-restart-p8mrt -n ns-zklqi check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-restart-p8mrt ns-zklqi Restart vastbase-rqfsww vastbase Creating -/- Sep 11,2025 18:22 UTC+0800 check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Updating Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase 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 vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 18:25 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 18:23 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 18:22 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check cluster connect done check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-restart-p8mrt ns-zklqi Restart vastbase-rqfsww vastbase Succeed 3/3 Sep 11,2025 18:22 UTC+0800 check ops status done ops_status:vastbase-rqfsww-restart-p8mrt ns-zklqi Restart vastbase-rqfsww vastbase Succeed 3/3 Sep 11,2025 18:22 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vastbase-rqfsww-restart-p8mrt --namespace ns-zklqi ` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-restart-p8mrt patched `kbcli cluster delete-ops --name vastbase-rqfsww-restart-p8mrt --force --auto-approve --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-restart-p8mrt deleted `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check db_client batch data Success cluster does not need to check monitor currently check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 18:25 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 18:23 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 18:22 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check cluster connect done test failover dnsrandom check cluster status before cluster-failover-dnsrandom check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnsrandom-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): dnschaos.chaos-mesh.org "test-chaos-mesh-dnsrandom-vastbase-rqfsww" not found Error from server (NotFound): dnschaos.chaos-mesh.org "test-chaos-mesh-dnsrandom-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: DNSChaos metadata: name: test-chaos-mesh-dnsrandom-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-1 mode: all action: random duration: 2m `kubectl apply -f test-chaos-mesh-dnsrandom-vastbase-rqfsww.yaml` dnschaos.chaos-mesh.org/test-chaos-mesh-dnsrandom-vastbase-rqfsww created apply test-chaos-mesh-dnsrandom-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-dnsrandom-vastbase-rqfsww.yaml` dnsrandom chaos test waiting 120 seconds check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 18:25 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 18:23 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 500m / 500m 2Gi / 2Gi data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 18:22 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-1;Standby: vastbase-rqfsww-vastbase-0 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnsrandom-vastbase-rqfsww --namespace ns-zklqi ` 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. dnschaos.chaos-mesh.org "test-chaos-mesh-dnsrandom-vastbase-rqfsww" force deleted dnschaos.chaos-mesh.org/test-chaos-mesh-dnsrandom-vastbase-rqfsww patched check failover pod name failover pod name:vastbase-rqfsww-vastbase-1 failover dnsrandom Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-1 --namespace ns-zklqi -- bash` check db_client batch data Success check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale vastbase-rqfsww --auto-approve --force=true --components vastbase --cpu 600m --memory 2.1Gi --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-verticalscaling-kbbvw created successfully, you can view the progress: kbcli cluster describe-ops vastbase-rqfsww-verticalscaling-kbbvw -n ns-zklqi check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-verticalscaling-kbbvw ns-zklqi VerticalScaling vastbase-rqfsww vastbase Creating -/- Sep 11,2025 18:28 UTC+0800 check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Updating Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase 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 vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 18:30 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 18:32 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 18:29 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-verticalscaling-kbbvw ns-zklqi VerticalScaling vastbase-rqfsww vastbase Succeed 3/3 Sep 11,2025 18:28 UTC+0800 check ops status done ops_status:vastbase-rqfsww-verticalscaling-kbbvw ns-zklqi VerticalScaling vastbase-rqfsww vastbase Succeed 3/3 Sep 11,2025 18:28 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vastbase-rqfsww-verticalscaling-kbbvw --namespace ns-zklqi ` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-verticalscaling-kbbvw patched `kbcli cluster delete-ops --name vastbase-rqfsww-verticalscaling-kbbvw --force --auto-approve --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-verticalscaling-kbbvw deleted `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check db_client batch data Success test failover timeoffset check cluster status before cluster-failover-timeoffset check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge TimeChaos test-chaos-mesh-timeoffset-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): timechaos.chaos-mesh.org "test-chaos-mesh-timeoffset-vastbase-rqfsww" not found Error from server (NotFound): timechaos.chaos-mesh.org "test-chaos-mesh-timeoffset-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: TimeChaos metadata: name: test-chaos-mesh-timeoffset-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-0 mode: all timeOffset: '-10m' clockIds: - CLOCK_REALTIME duration: 2m `kubectl apply -f test-chaos-mesh-timeoffset-vastbase-rqfsww.yaml` timechaos.chaos-mesh.org/test-chaos-mesh-timeoffset-vastbase-rqfsww created apply test-chaos-mesh-timeoffset-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-timeoffset-vastbase-rqfsww.yaml` timeoffset chaos test waiting 120 seconds check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 18:30 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 18:32 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 18:29 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge TimeChaos test-chaos-mesh-timeoffset-vastbase-rqfsww --namespace ns-zklqi ` 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. timechaos.chaos-mesh.org "test-chaos-mesh-timeoffset-vastbase-rqfsww" force deleted timechaos.chaos-mesh.org/test-chaos-mesh-timeoffset-vastbase-rqfsww patched check failover pod name failover pod name:vastbase-rqfsww-vastbase-0 failover timeoffset Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check db_client batch data Success test failover fullcpu check cluster status before cluster-failover-fullcpu check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-fullcpu-vastbase-rqfsww --namespace ns-zklqi ` 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. Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-fullcpu-vastbase-rqfsww" not found Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-fullcpu-vastbase-rqfsww" not found apiVersion: chaos-mesh.org/v1alpha1 kind: StressChaos metadata: name: test-chaos-mesh-fullcpu-vastbase-rqfsww namespace: ns-zklqi spec: selector: namespaces: - ns-zklqi labelSelectors: apps.kubeblocks.io/pod-name: vastbase-rqfsww-vastbase-0 mode: all stressors: cpu: workers: 100 load: 100 duration: 2m `kubectl apply -f test-chaos-mesh-fullcpu-vastbase-rqfsww.yaml` stresschaos.chaos-mesh.org/test-chaos-mesh-fullcpu-vastbase-rqfsww created apply test-chaos-mesh-fullcpu-vastbase-rqfsww.yaml Success `rm -rf test-chaos-mesh-fullcpu-vastbase-rqfsww.yaml` fullcpu chaos test waiting 120 seconds check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 18:30 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 18:32 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 18:29 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-fullcpu-vastbase-rqfsww --namespace ns-zklqi ` 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. stresschaos.chaos-mesh.org "test-chaos-mesh-fullcpu-vastbase-rqfsww" force deleted stresschaos.chaos-mesh.org/test-chaos-mesh-fullcpu-vastbase-rqfsww patched check failover pod name failover pod name:vastbase-rqfsww-vastbase-0 failover fullcpu Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check db_client batch data Success cluster update terminationPolicy WipeOut `kbcli cluster update vastbase-rqfsww --termination-policy=WipeOut --namespace ns-zklqi ` cluster.apps.kubeblocks.io/vastbase-rqfsww updated (no change) check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 18:30 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 18:32 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 18:29 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done LB_TYPE is set to: intranet cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose vastbase-rqfsww --auto-approve --force=true --type intranet --enable false --components vastbase --role-selector Primary --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-expose-jwn74 created successfully, you can view the progress: kbcli cluster describe-ops vastbase-rqfsww-expose-jwn74 -n ns-zklqi check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-expose-jwn74 ns-zklqi Expose vastbase-rqfsww Creating -/- Sep 11,2025 18:37 UTC+0800 check cluster status `kbcli cluster list vastbase-rqfsww --show-labels --namespace ns-zklqi ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vastbase-rqfsww ns-zklqi vastbase WipeOut Running Sep 11,2025 17:22 UTC+0800 app.kubernetes.io/instance=vastbase-rqfsww,clusterdefinition.kubeblocks.io/name=vastbase check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vastbase-rqfsww --namespace ns-zklqi ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vastbase-rqfsww-vastbase-0 ns-zklqi vastbase-rqfsww vastbase Running Primary 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000004/10.224.0.7 Sep 11,2025 18:30 UTC+0800 vastbase-rqfsww-vastbase-1 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000002/10.224.0.5 Sep 11,2025 18:32 UTC+0800 vastbase-rqfsww-vastbase-2 ns-zklqi vastbase-rqfsww vastbase Running Standby 0 600m / 600m 2254857830400m / 2254857830400m data:25Gi aks-cicdamdpool-27918866-vmss000001/10.224.0.9 Sep 11,2025 18:29 UTC+0800 check pod status done check cluster role check cluster role done Primary: vastbase-rqfsww-vastbase-0;Standby: vastbase-rqfsww-vastbase-1 vastbase-rqfsww-vastbase-2 `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check cluster connect `echo "psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check cluster connect done check ops status `kbcli cluster list-ops vastbase-rqfsww --status all --namespace ns-zklqi ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vastbase-rqfsww-expose-jwn74 ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 18:37 UTC+0800 ops_status:vastbase-rqfsww-expose-jwn74 ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 18:37 UTC+0800 ops_status:vastbase-rqfsww-expose-jwn74 ns-zklqi Expose vastbase-rqfsww vastbase Running 0/1 Sep 11,2025 18:37 UTC+0800 check ops status done ops_status:vastbase-rqfsww-expose-jwn74 ns-zklqi Expose vastbase-rqfsww vastbase Succeed 1/1 Sep 11,2025 18:37 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vastbase-rqfsww-expose-jwn74 --namespace ns-zklqi ` opsrequest.operations.kubeblocks.io/vastbase-rqfsww-expose-jwn74 patched `kbcli cluster delete-ops --name vastbase-rqfsww-expose-jwn74 --force --auto-approve --namespace ns-zklqi ` OpsRequest vastbase-rqfsww-expose-jwn74 deleted `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres `echo "echo \"SELECT value FROM tmp_table WHERE id = 1;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d postgres -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check data: Defaulted container "vastbase" out of: vastbase, kbagent, config-manager, init-kbagent (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- gzrea (1 row) check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=vastbase-rqfsww` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.username***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.password***"` `kubectl get secrets vastbase-rqfsww-vastbase-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:c7a1hn01L5FB996N;DB_PORT:5432;DB_DATABASE:postgres check db_client batch data count `echo "echo \"select count(*) from executions_loop_table;\" | psql -h vastbase-rqfsww-vastbase.ns-zklqi.svc.cluster.local -U root -p 5432 -d executions_loop -W 'c7a1hn01L5FB996N' " | kubectl exec -it vastbase-rqfsww-vastbase-0 --namespace ns-zklqi -- bash` check db_client batch data Success delete cluster vastbase-rqfsww `kbcli cluster delete vastbase-rqfsww --auto-approve --namespace ns-zklqi ` Cluster vastbase-rqfsww deleted secret "vastbase-rqfsww-license" deleted pod_info:vastbase-rqfsww-vastbase-0 3/3 Running 0 7m31s vastbase-rqfsww-vastbase-1 3/3 Running 0 5m59s vastbase-rqfsww-vastbase-2 3/3 Running 0 8m56s No resources found in ns-zklqi namespace. delete cluster pod done No resources found in ns-zklqi namespace. check cluster resource non-exist OK: pvc No resources found in ns-zklqi namespace. delete cluster done No resources found in ns-zklqi namespace. No resources found in ns-zklqi namespace. No resources found in ns-zklqi namespace. Vastbase Test Suite All Done! Test Engine: vastbase Test Type: 59 --------------------------------------Vastbase (Topology = Replicas 3) Test Result-------------------------------------- [PASSED]|[Create]|[ComponentDefinition=vastbase-2.2-1.0.1;ComponentVersion=vastbase;ServiceVersion=2.2.15;]|[Description=Create a cluster with the specified component definition vastbase-2.2-1.0.1 and component version vastbase and service version 2.2.15] [PASSED]|[Connect]|[ComponentName=vastbase]|[Description=Connect to the cluster] [PASSED]|[AddData]|[Values=gzrea]|[Description=Add data to the cluster] [PASSED]|[Expose]|[Enable=true;TYPE=intranet;ComponentName=vastbase]|[Description=Expose Enable the intranet service with vastbase component] [PASSED]|[No-Failover]|[HA=DNS Error;Durations=2m;ComponentName=vastbase]|[Description=Simulates conditions where pods experience DNS service errors for a period of time either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to DNS service errors.] [PASSED]|[VolumeExpansion]|[ComponentName=vastbase]|[Description=VolumeExpansion the cluster specify component vastbase] [PASSED]|[No-Failover]|[HA=Network Partition;Durations=2m;ComponentName=vastbase]|[Description=Simulates network partition fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to partition network.] [PASSED]|[Failover]|[HA=Network Loss;Durations=2m;ComponentName=vastbase]|[Description=Simulates network loss fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to loss network.] [PASSED]|[Failover]|[HA=Pod Kill;ComponentName=vastbase]|[Description=Simulates conditions where pods experience kill for a period of time either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to kill.] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [PASSED]|[No-Failover]|[HA=Network Duplicate;Durations=2m;ComponentName=vastbase]|[Description=Simulates network duplicate fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to duplicate network.] [PASSED]|[Failover]|[HA=OOM;Durations=2m;ComponentName=vastbase]|[Description=Simulates conditions where pods experience OOM either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to high Memory load.] [PASSED]|[SwitchOver]|[ComponentName=vastbase]|[Description=SwitchOver the cluster specify component vastbase] [PASSED]|[Bench]|[ComponentName=vastbase]|[Description=Bench the cluster service with vastbase component] [PASSED]|[Bench]|[HostType=LB;ComponentName=vastbase]|[Description=Bench the cluster LB service with vastbase component] [WARNING]|[CheckFailover]|[FailoverType=networkbandwidth]|[Description=-] [PASSED]|[Failover]|[HA=Network Bandwidth;Durations=2m;ComponentName=vastbase]|[Description=Simulates network bandwidth fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to bandwidth network.] [PASSED]|[HorizontalScaling Out]|[ComponentName=vastbase]|[Description=HorizontalScaling Out the cluster specify component vastbase] [PASSED]|[HorizontalScaling In]|[ComponentName=vastbase]|[Description=HorizontalScaling In the cluster specify component vastbase] [PASSED]|[Failover]|[HA=Pod Failure;Durations=2m;ComponentName=vastbase]|[Description=Simulates conditions where pods experience failure for a period of time either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to failure.] [PASSED]|[Reconfiguring]|[ComponentName=vastbase;audit_buffer_fflush_interval=150]|[Description=Reconfiguring the cluster specify component vastbase set audit_buffer_fflush_interval=150] [PASSED]|[No-Failover]|[HA=Network Delay;Durations=2m;ComponentName=vastbase]|[Description=Simulates network delay fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to delay network.] [PASSED]|[No-Failover]|[HA=Connection Stress;ComponentName=vastbase]|[Description=Simulates conditions where pods experience connection stress either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to high Connection load.] [PASSED]|[Failover]|[HA=Network Corrupt;Durations=2m;ComponentName=vastbase]|[Description=Simulates network corrupt fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to corrupt network.] [PASSED]|[Restart]|[-]|[Description=Restart the cluster] [PASSED]|[Update]|[Monitor=true]|[Description=Update the cluster Monitor enable] [PASSED]|[No-Failover]|[HA=DNS Random;Durations=2m;ComponentName=vastbase]|[Description=Simulates conditions where pods experience random IP addresses being returned by the DNS service for a period of time either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to the DNS service returning random IP addresses.] [PASSED]|[VerticalScaling]|[ComponentName=vastbase]|[Description=VerticalScaling the cluster specify component vastbase] [PASSED]|[No-Failover]|[HA=Time Offset;Durations=2m;ComponentName=vastbase]|[Description=Simulates a time offset scenario thereby testing the application's resilience to potential slowness/unavailability of some replicas due to time offset.] [PASSED]|[No-Failover]|[HA=Full CPU;Durations=2m;ComponentName=vastbase]|[Description=Simulates conditions where pods experience CPU full either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to high CPU load.] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Expose]|[Disable=true;TYPE=intranet;ComponentName=vastbase]|[Description=Expose Disable the intranet service with vastbase component] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]