bash test/kbcli/test_kbcli_0.9.sh --type 45 --version 0.9.5 --generate-output true --chaos-mesh true --drain-node true --random-namespace true --region eastus --cloud-provider aks CURRENT_TEST_DIR:test/kbcli source commons files source engines files source kubeblocks files `kubectl get namespace | grep ns-duzkg ` `kubectl create namespace ns-duzkg` namespace/ns-duzkg created create namespace ns-duzkg done download kbcli `gh release list --repo apecloud/kbcli --limit 100 | (grep "0.9" || true)` `curl -fsSL https://kubeblocks.io/installer/install_cli.sh | bash -s v0.9.5-beta.8` 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 100 32.1M 100 32.1M 0 0 108M 0 --:--:-- --:--:-- --:--:-- 108M kbcli installed successfully. Kubernetes: v1.32.6 KubeBlocks: 0.9.5 kbcli: 0.9.5-beta.8 WARNING: version difference between kbcli (0.9.5-beta.8) and kubeblocks (0.9.5) 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 v0.9.5-beta.8 done Kubernetes: v1.32.6 KubeBlocks: 0.9.5 kbcli: 0.9.5-beta.8 WARNING: version difference between kbcli (0.9.5-beta.8) and kubeblocks (0.9.5) Kubernetes Env: v1.32.6 POD_RESOURCES: aks kb-default-sc found aks default-vsc found found default storage class: default kubeblocks version is:0.9.5 skip upgrade kubeblocks 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 cluster definition set component name:fe set component version set component version:starrocks-be set service versions:3.2.2,3.3.0,3.3.2,3.3.3,3.4.1 set service versions sorted:3.2.2,3.3.0,3.3.2,3.3.3,3.4.1 no cluster version found REPORT_COUNT 0:0 set replicas first:2,3.2.2|2,3.3.0|2,3.3.2|2,3.3.3|2,3.4.1 set replicas third:2,3.4.1 set replicas fourth:2,3.2.2 set minimum cmpv service version set minimum cmpv service version replicas:2,3.2.2 REPORT_COUNT:1 CLUSTER_TOPOLOGY:shared-data topology shared-data found in cluster definition starrocks LIMIT_CPU:1 LIMIT_MEMORY:2 storage size: 20 No resources found in ns-duzkg namespace. termination_policy:Delete create 2 replica Delete starrocks cluster check cluster definition check component definition set component definition by component version check cmpd by labels set component definition2: starrocks-be by component version:starrocks-be apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: strent-mmdeab namespace: ns-duzkg spec: clusterDefinitionRef: starrocks topology: shared-data terminationPolicy: Delete componentSpecs: - name: cn serviceVersion: 3.2.2 serviceAccountName: kb-strent-mmdeab replicas: 2 resources: requests: cpu: 1000m memory: 2Gi limits: cpu: 1000m memory: 2Gi - name: fe serviceVersion: 3.2.2 serviceAccountName: kb-strent-mmdeab replicas: 3 resources: requests: cpu: 1000m memory: 2Gi limits: cpu: 1000m memory: 2Gi volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi `kubectl apply -f test_create_strent-mmdeab.yaml` cluster.apps.kubeblocks.io/strent-mmdeab created apply test_create_strent-mmdeab.yaml Success `rm -rf test_create_strent-mmdeab.yaml` check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Sep 01,2025 11:18 UTC+0800 clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= cluster_status: cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:21 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:21 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check pod strent-mmdeab-cn-0 container_name cn exist password 8139we0aMV check pod strent-mmdeab-cn-0 container_name nginx exist password 8139we0aMV check pod strent-mmdeab-cn-0 container_name lorry exist password 8139we0aMV check pod strent-mmdeab-cn-0 container_name config-manager exist password 8139we0aMV No container logs contain secret password. describe cluster `kbcli cluster describe strent-mmdeab --namespace ns-duzkg ` Name: strent-mmdeab Created Time: Sep 01,2025 11:18 UTC+0800 NAMESPACE CLUSTER-DEFINITION VERSION STATUS TERMINATION-POLICY ns-duzkg starrocks Running Delete Endpoints: COMPONENT MODE INTERNAL EXTERNAL fe ReadWrite strent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local:8030 strent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local:9030 cn ReadWrite strent-mmdeab-cn-cn.ns-duzkg.svc.cluster.local:8040 strent-mmdeab-cn-cn.ns-duzkg.svc.cluster.local:8080 Topology: COMPONENT INSTANCE ROLE STATUS AZ NODE CREATED-TIME cn strent-mmdeab-cn-0 Running 0 aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:21 UTC+0800 cn strent-mmdeab-cn-1 Running 0 aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:21 UTC+0800 fe strent-mmdeab-fe-0 Running 0 aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 fe strent-mmdeab-fe-1 Running 0 aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 fe strent-mmdeab-fe-2 Running 0 aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 Resources Allocation: COMPONENT DEDICATED CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS fe false 1 / 1 2Gi / 2Gi data:20Gi default cn false 1 / 1 2Gi / 2Gi Images: COMPONENT TYPE IMAGE fe docker.io/apecloud/fe-ubuntu:3.2.2 cn docker.io/apecloud/cn-ubuntu:3.2.2 Show cluster events: kbcli cluster list-events -n ns-duzkg strent-mmdeab `kbcli cluster label strent-mmdeab app.kubernetes.io/instance- --namespace ns-duzkg ` label "app.kubernetes.io/instance" not found. `kbcli cluster label strent-mmdeab app.kubernetes.io/instance=strent-mmdeab --namespace ns-duzkg ` `kbcli cluster label strent-mmdeab --list --namespace ns-duzkg ` NAME NAMESPACE LABELS strent-mmdeab ns-duzkg app.kubernetes.io/instance=strent-mmdeab clusterdefinition.kubeblocks.io/name=starrocks clusterversion.kubeblocks.io/name= label cluster app.kubernetes.io/instance=strent-mmdeab Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=strent-mmdeab --namespace ns-duzkg ` `kbcli cluster label strent-mmdeab --list --namespace ns-duzkg ` NAME NAMESPACE LABELS strent-mmdeab ns-duzkg app.kubernetes.io/instance=strent-mmdeab case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=starrocks clusterversion.kubeblocks.io/name= label cluster case.name=kbcli.test1 Success `kbcli cluster label strent-mmdeab case.name=kbcli.test2 --overwrite --namespace ns-duzkg ` `kbcli cluster label strent-mmdeab --list --namespace ns-duzkg ` NAME NAMESPACE LABELS strent-mmdeab ns-duzkg app.kubernetes.io/instance=strent-mmdeab case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=starrocks clusterversion.kubeblocks.io/name= label cluster case.name=kbcli.test2 Success `kbcli cluster label strent-mmdeab case.name- --namespace ns-duzkg ` `kbcli cluster label strent-mmdeab --list --namespace ns-duzkg ` NAME NAMESPACE LABELS strent-mmdeab ns-duzkg app.kubernetes.io/instance=strent-mmdeab clusterdefinition.kubeblocks.io/name=starrocks clusterversion.kubeblocks.io/name= delete cluster label case.name Success cluster connect `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys KUBEBLOCKS NAMESPACE:kb-sbbly get kubeblocks namespace done `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-sbbly -o jsonpath="***.items[0].data.root-user***"` `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-sbbly -o jsonpath="***.items[0].data.root-password***"` minio_user:kbclitest,minio_password:kbclitest,minio_endpoint:kbcli-test-minio.kb-sbbly.svc.cluster.local:9000 list minio bucket kbcli-test `echo 'mc config host add minioserver http://kbcli-test-minio.kb-sbbly.svc.cluster.local:9000 kbclitest kbclitest;mc ls minioserver' | kubectl exec -it kbcli-test-minio-78b4d7d7c9-zxt2r --namespace kb-sbbly -- bash` Unable to use a TTY - input is not a terminal or the right kind of file list minio bucket done `echo "echo \" CREATE STORAGE VOLUME sr_gxpat TYPE = S3 LOCATIONS = ('s3://kbcli-test/') PROPERTIES ( 'enabled' = 'true', 'aws.s3.endpoint' = 'http://kbcli-test-minio.kb-sbbly.svc.cluster.local:9000', 'aws.s3.access_key' = 'kbclitest', 'aws.s3.secret_key' = 'kbclitest' ); SET sr_gxpat AS DEFAULT STORAGE VOLUME; \" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash ` Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. connect cluster Success insert batch data by db client Error from server (NotFound): pods "test-db-client-executionloop-strent-mmdeab" not found DB_CLIENT_BATCH_DATA_COUNT: `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-executionloop-strent-mmdeab --namespace ns-duzkg ` Error from server (NotFound): pods "test-db-client-executionloop-strent-mmdeab" 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-strent-mmdeab" not found `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys apiVersion: v1 kind: Pod metadata: name: test-db-client-executionloop-strent-mmdeab namespace: ns-duzkg spec: containers: - name: test-dbclient imagePullPolicy: IfNotPresent image: docker.io/apecloud/dbclient:test args: - "--host" - "strent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local" - "--user" - "root" - "--password" - "8139we0aMV" - "--port" - "9030" - "--dbtype" - "starrocks" - "--test" - "executionloop" - "--duration" - "60" - "--interval" - "1" restartPolicy: Never `kubectl apply -f test-db-client-executionloop-strent-mmdeab.yaml` pod/test-db-client-executionloop-strent-mmdeab created apply test-db-client-executionloop-strent-mmdeab.yaml Success `rm -rf test-db-client-executionloop-strent-mmdeab.yaml` check pod status pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 0/1 ContainerCreating 0 5s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 9s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 15s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 20s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 25s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 30s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 35s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 40s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 45s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 50s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 55s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 61s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 1/1 Running 0 66s check pod test-db-client-executionloop-strent-mmdeab status done pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-strent-mmdeab 0/1 Completed 0 71s check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Running Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:21 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:21 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done --host strent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local --user root --password 8139we0aMV --port 9030 --dbtype starrocks --test executionloop --duration 60 --interval 1 SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider] Execution loop start: create databases executions_loop CREATE DATABASE IF NOT EXISTS executions_loop; drop table executions_loop_table DROP TABLE IF EXISTS executions_loop.executions_loop_table; create table executions_loop_table CREATE TABLE IF NOT EXISTS executions_loop.executions_loop_table (id INT, value VARCHAR(255), tinyint_col TINYINT, smallint_col SMALLINT, int_col INT, bigint_col BIGINT, float_col FLOAT, double_col DOUBLE, decimal_col DECIMAL(10, 2), date_col DATE, datetime_col DATETIME, char_col CHAR(10), text_col TEXT, binary_col BINARY(30), varbinary_col VARBINARY(255), enum_col VARCHAR(20), set_col VARCHAR(50) ) ENGINE=OLAP DUPLICATE KEY(id) DISTRIBUTED BY HASH(id) BUCKETS 3 PROPERTIES ( 'replication_num' = '1' ); Execution loop start:INSERT INTO executions_loop.executions_loop_table (value, tinyint_col, smallint_col, int_col, bigint_col, float_col, double_col, decimal_col, date_col, datetime_col, char_col, text_col, binary_col, varbinary_col, enum_col, set_col) VALUES ('executions_loop_test_1', 45, 14995, -730543156, -7929653302930574344, 0.81667286, 0.8216317275440149, 3.982861415720862, '2025-09-01', '2025-09-01 03:23:39.253', 'dCBEKTBeaq', '0tt3nHuHeApGDRbtPfARVGZG0IbOO0JuHgqVSSnAWRQMyQOvfzd9uXhiva69JOZNJctcGc133x1RK2g6Sh9aMPXuiEPJG0qGkrrDX69xLB8e25UGQ3V1pd9ZjSK2UtMPQUbuEgluiY9EYt0ShWwbh9rLmHgXmfDbR0j65WfkAiermrBMpePM9ZCiTks11NWjyfRqH9W17utoLwisvpepi8s4LV5mEr0QztsyblikvzKYjkMWjAPtH0v6mbzpoRh', TO_BINARY('base64,4P679+brnS2OyA=='), TO_BINARY('base64,Yb0cwsRJqe5i+p5f/N0Oz3VhQ53ka6NZ74mi5+uKH8pYRZhq+mIfGPmzxp6nqlk6RG+jQle1553y0GH2N/IMhvs7DSHzXYuQ4vTGoo2MI+romJIdxuXGRCIwN5/4xbqUhDwAkFU+VXljmJ813HrWdPuA/tqPMVud9V1AcKU9UE4Oxe1Z2Xp5IEZxWer5Z769O3etl2bdvhaofL0='), 'Option1', 'Value2' ); [ 1s ] executions total: 1 successful: 1 failed: 0 disconnect: 0 [ 2s ] executions total: 6 successful: 6 failed: 0 disconnect: 0 [ 3s ] executions total: 14 successful: 14 failed: 0 disconnect: 0 [ 4s ] executions total: 17 successful: 17 failed: 0 disconnect: 0 [ 5s ] executions total: 25 successful: 25 failed: 0 disconnect: 0 [ 6s ] executions total: 34 successful: 34 failed: 0 disconnect: 0 [ 7s ] executions total: 43 successful: 43 failed: 0 disconnect: 0 [ 8s ] executions total: 52 successful: 52 failed: 0 disconnect: 0 [ 9s ] executions total: 58 successful: 58 failed: 0 disconnect: 0 [ 10s ] executions total: 67 successful: 67 failed: 0 disconnect: 0 [ 11s ] executions total: 76 successful: 76 failed: 0 disconnect: 0 [ 12s ] executions total: 84 successful: 84 failed: 0 disconnect: 0 [ 13s ] executions total: 93 successful: 93 failed: 0 disconnect: 0 [ 14s ] executions total: 102 successful: 102 failed: 0 disconnect: 0 [ 15s ] executions total: 111 successful: 111 failed: 0 disconnect: 0 [ 16s ] executions total: 120 successful: 120 failed: 0 disconnect: 0 [ 17s ] executions total: 127 successful: 127 failed: 0 disconnect: 0 [ 18s ] executions total: 136 successful: 136 failed: 0 disconnect: 0 [ 19s ] executions total: 145 successful: 145 failed: 0 disconnect: 0 [ 20s ] executions total: 155 successful: 155 failed: 0 disconnect: 0 [ 21s ] executions total: 165 successful: 165 failed: 0 disconnect: 0 [ 22s ] executions total: 172 successful: 172 failed: 0 disconnect: 0 [ 23s ] executions total: 181 successful: 181 failed: 0 disconnect: 0 [ 24s ] executions total: 190 successful: 190 failed: 0 disconnect: 0 [ 25s ] executions total: 200 successful: 200 failed: 0 disconnect: 0 [ 26s ] executions total: 209 successful: 209 failed: 0 disconnect: 0 [ 27s ] executions total: 219 successful: 219 failed: 0 disconnect: 0 [ 28s ] executions total: 227 successful: 227 failed: 0 disconnect: 0 [ 29s ] executions total: 237 successful: 237 failed: 0 disconnect: 0 [ 30s ] executions total: 246 successful: 246 failed: 0 disconnect: 0 [ 31s ] executions total: 255 successful: 255 failed: 0 disconnect: 0 [ 32s ] executions total: 263 successful: 263 failed: 0 disconnect: 0 [ 33s ] executions total: 273 successful: 273 failed: 0 disconnect: 0 [ 34s ] executions total: 283 successful: 283 failed: 0 disconnect: 0 [ 35s ] executions total: 293 successful: 293 failed: 0 disconnect: 0 [ 36s ] executions total: 303 successful: 303 failed: 0 disconnect: 0 [ 37s ] executions total: 313 successful: 313 failed: 0 disconnect: 0 [ 38s ] executions total: 320 successful: 320 failed: 0 disconnect: 0 [ 39s ] executions total: 330 successful: 330 failed: 0 disconnect: 0 [ 60s ] executions total: 331 successful: 331 failed: 0 disconnect: 0 Test Result: Total Executions: 331 Successful Executions: 331 Failed Executions: 0 Disconnection Counts: 0 Connection Information: Database Type: starrocks Host: strent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local Port: 9030 Database: Table: User: root Org: Access Mode: mysql Test Type: executionloop Query: Duration: 60 seconds Interval: 1 seconds DB_CLIENT_BATCH_DATA_COUNT: 331 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-executionloop-strent-mmdeab --namespace ns-duzkg ` pod/test-db-client-executionloop-strent-mmdeab 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-strent-mmdeab" force deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo \"CREATE DATABASE IF NOT EXISTS mydb; use mydb; DROP TABLE IF EXISTS tmp_table; CREATE TABLE IF NOT EXISTS tmp_table (id INT, value STRING) ; INSERT INTO tmp_table (id, value) VALUES (1,'bkzlo');\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. add consistent data bkzlo Success cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose strent-mmdeab --auto-approve --force=true --type internet --enable true --components fe --namespace ns-duzkg ` OpsRequest strent-mmdeab-expose-rx9q7 created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-expose-rx9q7 -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-expose-rx9q7 ns-duzkg Expose strent-mmdeab Pending -/- Sep 01,2025 11:24 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Running Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:21 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:21 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-expose-rx9q7 ns-duzkg Expose strent-mmdeab fe Running 0/1 Sep 01,2025 11:24 UTC+0800 ops_status:strent-mmdeab-expose-rx9q7 ns-duzkg Expose strent-mmdeab fe Running 0/1 Sep 01,2025 11:24 UTC+0800 check ops status done ops_status:strent-mmdeab-expose-rx9q7 ns-duzkg Expose strent-mmdeab fe Succeed 1/1 Sep 01,2025 11:24 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-expose-rx9q7 --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-expose-rx9q7 patched `kbcli cluster delete-ops --name strent-mmdeab-expose-rx9q7 --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-expose-rx9q7 deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success skip Component cn VolumeExpansion cluster rebulid instances apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: strent-mmdeab-rebuildinstance- namespace: ns-duzkg spec: type: RebuildInstance clusterName: strent-mmdeab force: true rebuildFrom: - componentName: cn instances: - name: strent-mmdeab-cn-0 inPlace: true check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_strent-mmdeab.yaml` opsrequest.apps.kubeblocks.io/strent-mmdeab-rebuildinstance-pgnvw created create test_ops_cluster_strent-mmdeab.yaml Success `rm -rf test_ops_cluster_strent-mmdeab.yaml` check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-rebuildinstance-pgnvw ns-duzkg RebuildInstance strent-mmdeab Creating -/- Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-rebuildinstance-pgnvw ns-duzkg RebuildInstance strent-mmdeab Running -/- Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-rebuildinstance-pgnvw ns-duzkg RebuildInstance strent-mmdeab cn Running 0/1 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-rebuildinstance-pgnvw ns-duzkg RebuildInstance strent-mmdeab cn Running 0/1 Sep 01,2025 11:25 UTC+0800 check ops status done ops_status:strent-mmdeab-rebuildinstance-pgnvw ns-duzkg RebuildInstance strent-mmdeab cn Succeed 1/1 Sep 01,2025 11:25 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-rebuildinstance-pgnvw --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-rebuildinstance-pgnvw patched `kbcli cluster delete-ops --name strent-mmdeab-rebuildinstance-pgnvw --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-rebuildinstance-pgnvw deleted check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Running Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:25 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:21 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success check component fe exists `kubectl get components -l app.kubernetes.io/instance=strent-mmdeab,apps.kubeblocks.io/component-name=fe --namespace ns-duzkg | (grep "fe" || true )` cluster vscale check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale strent-mmdeab --auto-approve --force=true --components fe --cpu 1100m --memory 2.1Gi --namespace ns-duzkg ` OpsRequest strent-mmdeab-verticalscaling-tmnm7 created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-verticalscaling-tmnm7 -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Creating -/- Sep 01,2025 11:25 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Updating Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating [Error] check cluster status timeout --------------------------------------get cluster strent-mmdeab yaml-------------------------------------- `kubectl get cluster strent-mmdeab -o yaml --namespace ns-duzkg ` apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: annotations: kubeblocks.io/ops-request: '[***"name":"strent-mmdeab-verticalscaling-tmnm7","type":"VerticalScaling"***]' kubeblocks.io/reconcile: "2025-09-01T03:30:00.085774942Z" kubectl.kubernetes.io/last-applied-configuration: | ***"apiVersion":"apps.kubeblocks.io/v1alpha1","kind":"Cluster","metadata":***"annotations":***,"name":"strent-mmdeab","namespace":"ns-duzkg"***,"spec":***"clusterDefinitionRef":"starrocks","componentSpecs":[***"name":"cn","replicas":2,"resources":***"limits":***"cpu":"1000m","memory":"2Gi"***,"requests":***"cpu":"1000m","memory":"2Gi"***,"serviceAccountName":"kb-strent-mmdeab","serviceVersion":"3.2.2"***,***"name":"fe","replicas":3,"resources":***"limits":***"cpu":"1000m","memory":"2Gi"***,"requests":***"cpu":"1000m","memory":"2Gi"***,"serviceAccountName":"kb-strent-mmdeab","serviceVersion":"3.2.2","volumeClaimTemplates":[***"name":"data","spec":***"accessModes":["ReadWriteOnce"],"resources":***"requests":***"storage":"20Gi"***,"storageClassName":null***]***],"terminationPolicy":"Delete","topology":"shared-data"*** creationTimestamp: "2025-09-01T03:18:32Z" finalizers: - cluster.kubeblocks.io/finalizer generation: 6 labels: app.kubernetes.io/instance: strent-mmdeab clusterdefinition.kubeblocks.io/name: starrocks clusterversion.kubeblocks.io/name: "" name: strent-mmdeab namespace: ns-duzkg resourceVersion: "24473" uid: adba5cbb-a99b-4c60-9bc5-f1af75cdfbc7 spec: clusterDefinitionRef: starrocks componentSpecs: - componentDef: starrocks-fe-sd name: fe replicas: 3 resources: limits: cpu: 1100m memory: 2254857830400m requests: cpu: 1100m memory: 2254857830400m serviceAccountName: kb-strent-mmdeab serviceVersion: 3.2.2 volumeClaimTemplates: - name: data spec: accessModes: - ReadWriteOnce resources: requests: storage: 20Gi - componentDef: starrocks-cn name: cn replicas: 2 resources: limits: cpu: "1" memory: 2Gi requests: cpu: "1" memory: 2Gi serviceAccountName: kb-strent-mmdeab serviceVersion: 3.2.2 resources: cpu: "0" memory: "0" services: - annotations: service.beta.kubernetes.io/azure-load-balancer-internal: "false" componentSelector: fe name: fe-internet serviceName: fe-internet spec: ports: - name: fe-http nodePort: 30693 port: 8030 protocol: TCP targetPort: http-port - name: fe-mysql nodePort: 30772 port: 9030 protocol: TCP targetPort: query-port type: LoadBalancer storage: size: "0" terminationPolicy: Delete topology: shared-data status: clusterDefGeneration: 1 components: cn: phase: Running podsReady: true podsReadyTime: "2025-09-01T03:25:30Z" fe: phase: Updating podsReady: false podsReadyTime: "2025-09-01T03:21:29Z" conditions: - lastTransitionTime: "2025-09-01T03:18:32Z" message: 'The operator has started the provisioning of Cluster: strent-mmdeab' observedGeneration: 6 reason: PreCheckSucceed status: "True" type: ProvisioningStarted - lastTransitionTime: "2025-09-01T03:18:32Z" message: Successfully applied for resources observedGeneration: 6 reason: ApplyResourcesSucceed status: "True" type: ApplyResources - lastTransitionTime: "2025-09-01T03:25:46Z" message: 'pods are not ready in Components: [fe], refer to related component message in Cluster.status.components' reason: ReplicasNotReady status: "False" type: ReplicasReady - lastTransitionTime: "2025-09-01T03:25:46Z" message: 'pods are unavailable in Components: [fe], refer to related component message in Cluster.status.components' reason: ComponentsNotReady status: "False" type: Ready observedGeneration: 6 phase: Updating ------------------------------------------------------------------------------------------------------------------ --------------------------------------describe cluster strent-mmdeab-------------------------------------- `kubectl describe cluster strent-mmdeab --namespace ns-duzkg ` Name: strent-mmdeab Namespace: ns-duzkg Labels: app.kubernetes.io/instance=strent-mmdeab clusterdefinition.kubeblocks.io/name=starrocks clusterversion.kubeblocks.io/name= Annotations: kubeblocks.io/ops-request: [***"name":"strent-mmdeab-verticalscaling-tmnm7","type":"VerticalScaling"***] kubeblocks.io/reconcile: 2025-09-01T03:30:00.085774942Z API Version: apps.kubeblocks.io/v1alpha1 Kind: Cluster Metadata: Creation Timestamp: 2025-09-01T03:18:32Z Finalizers: cluster.kubeblocks.io/finalizer Generation: 6 Resource Version: 24473 UID: adba5cbb-a99b-4c60-9bc5-f1af75cdfbc7 Spec: Cluster Definition Ref: starrocks Component Specs: Component Def: starrocks-fe-sd Name: fe Replicas: 3 Resources: Limits: Cpu: 1100m Memory: 2254857830400m Requests: Cpu: 1100m Memory: 2254857830400m Service Account Name: kb-strent-mmdeab Service Version: 3.2.2 Volume Claim Templates: Name: data Spec: Access Modes: ReadWriteOnce Resources: Requests: Storage: 20Gi Component Def: starrocks-cn Name: cn Replicas: 2 Resources: Limits: Cpu: 1 Memory: 2Gi Requests: Cpu: 1 Memory: 2Gi Service Account Name: kb-strent-mmdeab Service Version: 3.2.2 Resources: Cpu: 0 Memory: 0 Services: Annotations: service.beta.kubernetes.io/azure-load-balancer-internal: false Component Selector: fe Name: fe-internet Service Name: fe-internet Spec: Ports: Name: fe-http Node Port: 30693 Port: 8030 Protocol: TCP Target Port: http-port Name: fe-mysql Node Port: 30772 Port: 9030 Protocol: TCP Target Port: query-port Type: LoadBalancer Storage: Size: 0 Termination Policy: Delete Topology: shared-data Status: Cluster Def Generation: 1 Components: Cn: Phase: Running Pods Ready: true Pods Ready Time: 2025-09-01T03:25:30Z Fe: Phase: Updating Pods Ready: false Pods Ready Time: 2025-09-01T03:21:29Z Conditions: Last Transition Time: 2025-09-01T03:18:32Z Message: The operator has started the provisioning of Cluster: strent-mmdeab Observed Generation: 6 Reason: PreCheckSucceed Status: True Type: ProvisioningStarted Last Transition Time: 2025-09-01T03:18:32Z Message: Successfully applied for resources Observed Generation: 6 Reason: ApplyResourcesSucceed Status: True Type: ApplyResources Last Transition Time: 2025-09-01T03:25:46Z Message: pods are not ready in Components: [fe], refer to related component message in Cluster.status.components Reason: ReplicasNotReady Status: False Type: ReplicasReady Last Transition Time: 2025-09-01T03:25:46Z Message: pods are unavailable in Components: [fe], refer to related component message in Cluster.status.components Reason: ComponentsNotReady Status: False Type: Ready Observed Generation: 6 Phase: Updating Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning Unhealthy 11m (x7 over 12m) event-controller Pod strent-mmdeab-fe-2: Startup probe failed: Get "http://10.244.1.68:8030/api/health": dial tcp 10.244.1.68:8030: connect: connection refused Warning Unhealthy 11m (x8 over 12m) event-controller Pod strent-mmdeab-fe-1: Startup probe failed: Get "http://10.244.1.216:8030/api/health": dial tcp 10.244.1.216:8030: connect: connection refused Normal ComponentPhaseTransition 11m (x2 over 14m) cluster-controller component is Creating Normal PreCheckSucceed 8m8s (x5 over 14m) cluster-controller The operator has started the provisioning of Cluster: strent-mmdeab Normal ApplyResourcesSucceed 8m8s (x5 over 14m) cluster-controller Successfully applied for resources Warning ReplicasNotReady 7m46s (x2 over 11m) cluster-controller pods are not ready in Components: [cn], refer to related component message in Cluster.status.components Warning ComponentsNotReady 7m46s (x2 over 11m) cluster-controller pods are unavailable in Components: [cn], refer to related component message in Cluster.status.components Normal ComponentPhaseTransition 7m46s cluster-controller component is Updating Normal ComponentPhaseTransition 7m35s (x3 over 11m) cluster-controller component is Running Normal AllReplicasReady 7m35s (x2 over 10m) cluster-controller all pods of components are ready, waiting for the probe detection successful Normal ClusterReady 7m35s (x2 over 10m) cluster-controller Cluster: strent-mmdeab is ready, current phase is Running Normal Running 7m35s (x2 over 10m) cluster-controller Cluster: strent-mmdeab is ready, current phase is Running Warning FailedAttachVolume 3m5s (x3 over 4m43s) event-controller Pod strent-mmdeab-fe-2: AttachVolume.Attach failed for volume "pvc-f7104c5d-f12a-4def-8c82-87deb16ba5dc" : volume attachment is being deleted ------------------------------------------------------------------------------------------------------------------ check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:25 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:21 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1 / 1 2Gi / 2Gi data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:18 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:32 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:25 UTC+0800 check pod status done check cluster status again check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 1/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 1/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 1/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 1/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 2/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 2/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 2/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 2/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 2/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 2/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 2/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 2/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 2/3 Sep 01,2025 11:25 UTC+0800 ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Running 3/3 Sep 01,2025 11:25 UTC+0800 check ops status done ops_status:strent-mmdeab-verticalscaling-tmnm7 ns-duzkg VerticalScaling strent-mmdeab fe Succeed 3/3 Sep 01,2025 11:25 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-verticalscaling-tmnm7 --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-verticalscaling-tmnm7 patched `kbcli cluster delete-ops --name strent-mmdeab-verticalscaling-tmnm7 --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-verticalscaling-tmnm7 deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop strent-mmdeab --auto-approve --force=true --namespace ns-duzkg ` OpsRequest strent-mmdeab-stop-nt6xk created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-stop-nt6xk -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-stop-nt6xk ns-duzkg Stop strent-mmdeab Pending -/- Sep 01,2025 11:34 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Stopping Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping check cluster status done cluster_status:Stopped check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` 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 strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-stop-nt6xk ns-duzkg Stop strent-mmdeab cn,fe Succeed 5/5 Sep 01,2025 11:34 UTC+0800 check ops status done ops_status:strent-mmdeab-stop-nt6xk ns-duzkg Stop strent-mmdeab cn,fe Succeed 5/5 Sep 01,2025 11:34 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-stop-nt6xk --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-stop-nt6xk patched `kbcli cluster delete-ops --name strent-mmdeab-stop-nt6xk --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-stop-nt6xk deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start strent-mmdeab --force=true --namespace ns-duzkg ` OpsRequest strent-mmdeab-start-rnlrh created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-start-rnlrh -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-start-rnlrh ns-duzkg Start strent-mmdeab Creating -/- Sep 01,2025 11:35 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Updating Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Abnormal cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:35 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:35 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:35 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:35 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:35 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-start-rnlrh ns-duzkg Start strent-mmdeab cn,fe Succeed 5/5 Sep 01,2025 11:35 UTC+0800 check ops status done ops_status:strent-mmdeab-start-rnlrh ns-duzkg Start strent-mmdeab cn,fe Succeed 5/5 Sep 01,2025 11:35 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-start-rnlrh --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-start-rnlrh patched `kbcli cluster delete-ops --name strent-mmdeab-start-rnlrh --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-start-rnlrh deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart strent-mmdeab --auto-approve --force=true --namespace ns-duzkg ` OpsRequest strent-mmdeab-restart-ft5vn created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-restart-ft5vn -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-restart-ft5vn ns-duzkg Restart strent-mmdeab fe,cn Creating -/- Sep 01,2025 11:38 UTC+0800 ops_status:strent-mmdeab-restart-ft5vn ns-duzkg Restart strent-mmdeab fe,cn Creating -/- Sep 01,2025 11:38 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Updating Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-restart-ft5vn ns-duzkg Restart strent-mmdeab fe,cn Succeed 5/5 Sep 01,2025 11:38 UTC+0800 check ops status done ops_status:strent-mmdeab-restart-ft5vn ns-duzkg Restart strent-mmdeab fe,cn Succeed 5/5 Sep 01,2025 11:38 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-restart-ft5vn --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-restart-ft5vn patched `kbcli cluster delete-ops --name strent-mmdeab-restart-ft5vn --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-restart-ft5vn deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success test failover connectionstress check cluster status before cluster-failover-connectionstress check cluster status done cluster_status:Running check node drain check node drain success Error from server (NotFound): pods "test-db-client-connectionstress-strent-mmdeab" not found `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-connectionstress-strent-mmdeab --namespace ns-duzkg ` Error from server (NotFound): pods "test-db-client-connectionstress-strent-mmdeab" 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-strent-mmdeab" not found `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys apiVersion: v1 kind: Pod metadata: name: test-db-client-connectionstress-strent-mmdeab namespace: ns-duzkg spec: containers: - name: test-dbclient imagePullPolicy: IfNotPresent image: docker.io/apecloud/dbclient:test args: - "--host" - "strent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local" - "--user" - "root" - "--password" - "8139we0aMV" - "--port" - "9030" - "--database" - "sys" - "--dbtype" - "starrocks" - "--test" - "connectionstress" - "--connections" - "200" - "--duration" - "60" restartPolicy: Never `kubectl apply -f test-db-client-connectionstress-strent-mmdeab.yaml` pod/test-db-client-connectionstress-strent-mmdeab created apply test-db-client-connectionstress-strent-mmdeab.yaml Success `rm -rf test-db-client-connectionstress-strent-mmdeab.yaml` check pod status pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-strent-mmdeab 1/1 Running 0 5s check pod test-db-client-connectionstress-strent-mmdeab status done pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-strent-mmdeab 0/1 Completed 0 9s check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Running Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1 / 1 2Gi / 2Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done --host strent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local --user root --password 8139we0aMV --port 9030 --database sys --dbtype starrocks --test connectionstress --connections 200 --duration 60 SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider] Test Result: null Connection Information: Database Type: starrocks Host: strent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local Port: 9030 Database: sys 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-strent-mmdeab --namespace ns-duzkg ` pod/test-db-client-connectionstress-strent-mmdeab 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-strent-mmdeab" force deleted check failover pod name failover pod name:strent-mmdeab-cn-0 failover connectionstress Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success cluster vscale check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale strent-mmdeab --auto-approve --force=true --components cn --cpu 1100m --memory 2.1Gi --namespace ns-duzkg ` OpsRequest strent-mmdeab-verticalscaling-5td5x created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-verticalscaling-5td5x -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-verticalscaling-5td5x ns-duzkg VerticalScaling strent-mmdeab cn Pending -/- Sep 01,2025 11:40 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Updating Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= 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 strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:38 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-verticalscaling-5td5x ns-duzkg VerticalScaling strent-mmdeab cn Succeed 2/2 Sep 01,2025 11:40 UTC+0800 check ops status done ops_status:strent-mmdeab-verticalscaling-5td5x ns-duzkg VerticalScaling strent-mmdeab cn Succeed 2/2 Sep 01,2025 11:40 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-verticalscaling-5td5x --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-verticalscaling-5td5x patched `kbcli cluster delete-ops --name strent-mmdeab-verticalscaling-5td5x --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-verticalscaling-5td5x deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success check component fe exists `kubectl get components -l app.kubernetes.io/instance=strent-mmdeab,apps.kubeblocks.io/component-name=fe --namespace ns-duzkg | (grep "fe" || true )` cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart strent-mmdeab --auto-approve --force=true --components fe --namespace ns-duzkg ` OpsRequest strent-mmdeab-restart-g52b8 created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-restart-g52b8 -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-restart-g52b8 ns-duzkg Restart strent-mmdeab fe Creating -/- Sep 01,2025 11:40 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Updating Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-restart-g52b8 ns-duzkg Restart strent-mmdeab fe Succeed 3/3 Sep 01,2025 11:40 UTC+0800 check ops status done ops_status:strent-mmdeab-restart-g52b8 ns-duzkg Restart strent-mmdeab fe Succeed 3/3 Sep 01,2025 11:40 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-restart-g52b8 --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-restart-g52b8 patched `kbcli cluster delete-ops --name strent-mmdeab-restart-g52b8 --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-restart-g52b8 deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success cluster hscale check cluster status before ops check cluster status done cluster_status:Running No resources found in strent-mmdeab namespace. `kbcli cluster hscale strent-mmdeab --auto-approve --force=true --components cn --replicas 3 --namespace ns-duzkg ` OpsRequest strent-mmdeab-horizontalscaling-njtf4 created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-horizontalscaling-njtf4 -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-horizontalscaling-njtf4 ns-duzkg HorizontalScaling strent-mmdeab cn Creating -/- Sep 01,2025 11:42 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Updating Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 strent-mmdeab-cn-2 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:42 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done No resources found in strent-mmdeab namespace. check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-horizontalscaling-njtf4 ns-duzkg HorizontalScaling strent-mmdeab cn Succeed 1/1 Sep 01,2025 11:42 UTC+0800 check ops status done ops_status:strent-mmdeab-horizontalscaling-njtf4 ns-duzkg HorizontalScaling strent-mmdeab cn Succeed 1/1 Sep 01,2025 11:42 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-horizontalscaling-njtf4 --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-horizontalscaling-njtf4 patched `kbcli cluster delete-ops --name strent-mmdeab-horizontalscaling-njtf4 --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-horizontalscaling-njtf4 deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success cluster hscale check cluster status before ops check cluster status done cluster_status:Running No resources found in strent-mmdeab namespace. `kbcli cluster hscale strent-mmdeab --auto-approve --force=true --components cn --replicas 2 --namespace ns-duzkg ` OpsRequest strent-mmdeab-horizontalscaling-pnjg9 created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-horizontalscaling-pnjg9 -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-horizontalscaling-pnjg9 ns-duzkg HorizontalScaling strent-mmdeab cn Creating -/- Sep 01,2025 11:42 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Updating Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done No resources found in strent-mmdeab namespace. check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-horizontalscaling-pnjg9 ns-duzkg HorizontalScaling strent-mmdeab cn Succeed 1/1 Sep 01,2025 11:42 UTC+0800 check ops status done ops_status:strent-mmdeab-horizontalscaling-pnjg9 ns-duzkg HorizontalScaling strent-mmdeab cn Succeed 1/1 Sep 01,2025 11:42 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-horizontalscaling-pnjg9 --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-horizontalscaling-pnjg9 patched `kbcli cluster delete-ops --name strent-mmdeab-horizontalscaling-pnjg9 --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-horizontalscaling-pnjg9 deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart strent-mmdeab --auto-approve --force=true --components cn --namespace ns-duzkg ` OpsRequest strent-mmdeab-restart-pdm6x created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-restart-pdm6x -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-restart-pdm6x ns-duzkg Restart strent-mmdeab cn Creating -/- Sep 01,2025 11:43 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Updating Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= 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 strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:43 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:43 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:20Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-restart-pdm6x ns-duzkg Restart strent-mmdeab cn Succeed 2/2 Sep 01,2025 11:43 UTC+0800 check ops status done ops_status:strent-mmdeab-restart-pdm6x ns-duzkg Restart strent-mmdeab cn Succeed 2/2 Sep 01,2025 11:43 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-restart-pdm6x --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-restart-pdm6x patched `kbcli cluster delete-ops --name strent-mmdeab-restart-pdm6x --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-restart-pdm6x deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data retry times: 1 check db_client batch data retry times: 2 check db_client batch data Success check component fe exists `kubectl get components -l app.kubernetes.io/instance=strent-mmdeab,apps.kubeblocks.io/component-name=fe --namespace ns-duzkg | (grep "fe" || true )` `kubectl get pvc -l app.kubernetes.io/instance=strent-mmdeab,apps.kubeblocks.io/component-name=fe,apps.kubeblocks.io/vct-name=data --namespace ns-duzkg ` cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in strent-mmdeab namespace. `kbcli cluster volume-expand strent-mmdeab --auto-approve --force=true --components fe --volume-claim-templates data --storage 22Gi --namespace ns-duzkg ` OpsRequest strent-mmdeab-volumeexpansion-8sr9r created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-volumeexpansion-8sr9r -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-volumeexpansion-8sr9r ns-duzkg VolumeExpansion strent-mmdeab fe Creating -/- Sep 01,2025 11:44 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks Delete Updating Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:43 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:43 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:22Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:22Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:22Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done No resources found in strent-mmdeab namespace. check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-volumeexpansion-8sr9r ns-duzkg VolumeExpansion strent-mmdeab fe Succeed 3/3 Sep 01,2025 11:44 UTC+0800 check ops status done ops_status:strent-mmdeab-volumeexpansion-8sr9r ns-duzkg VolumeExpansion strent-mmdeab fe Succeed 3/3 Sep 01,2025 11:44 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-volumeexpansion-8sr9r --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-volumeexpansion-8sr9r patched `kbcli cluster delete-ops --name strent-mmdeab-volumeexpansion-8sr9r --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-volumeexpansion-8sr9r deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success cluster list-logs `kbcli cluster list-logs strent-mmdeab --namespace ns-duzkg ` No log files found. You can enable the log feature with the kbcli command below. kbcli cluster update strent-mmdeab --enable-all-logs=true --namespace ns-duzkg Error from server (NotFound): pods "strent-mmdeab-cn-0" not found cluster logs `kbcli cluster logs strent-mmdeab --tail 30 --namespace ns-duzkg ` Defaulted container "cn" out of: cn, nginx, lorry, config-manager, init-lorry (init) [2025-09-01 11:43:56] strent-mmdeab-cn-0 is not in suspend list anymore, ready to start. [Mon Sep 1 11:43:56 CST 2025] Add myself (strent-mmdeab-cn-0.strent-mmdeab-cn-headless.ns-duzkg.svc.cluster.local:9050) into FE ... [Mon Sep 1 11:43:56 CST 2025] /etc/starrocks/cn/conf not exist or not a directory, ignore ... [Mon Sep 1 11:43:56 CST 2025] run start_cn.sh cluster update terminationPolicy WipeOut `kbcli cluster update strent-mmdeab --termination-policy=WipeOut --namespace ns-duzkg ` cluster.apps.kubeblocks.io/strent-mmdeab updated check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks WipeOut Running Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:43 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:43 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:22Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:22Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:22Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose strent-mmdeab --auto-approve --force=true --type internet --enable false --components fe --namespace ns-duzkg ` OpsRequest strent-mmdeab-expose-nzfwc created successfully, you can view the progress: kbcli cluster describe-ops strent-mmdeab-expose-nzfwc -n ns-duzkg check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-expose-nzfwc ns-duzkg Expose strent-mmdeab Pending -/- Sep 01,2025 12:06 UTC+0800 check cluster status `kbcli cluster list strent-mmdeab --show-labels --namespace ns-duzkg ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS strent-mmdeab ns-duzkg starrocks WipeOut Running Sep 01,2025 11:18 UTC+0800 app.kubernetes.io/instance=strent-mmdeab,clusterdefinition.kubeblocks.io/name=starrocks,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances strent-mmdeab --namespace ns-duzkg ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME strent-mmdeab-cn-0 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:43 UTC+0800 strent-mmdeab-cn-1 ns-duzkg strent-mmdeab cn Running 0 1100m / 1100m 2254857830400m / 2254857830400m aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:43 UTC+0800 strent-mmdeab-fe-0 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:22Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-1 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:22Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:41 UTC+0800 strent-mmdeab-fe-2 ns-duzkg strent-mmdeab fe Running 0 1100m / 1100m 2254857830400m / 2254857830400m data:22Gi aks-cicdamdpool-18448605-vmss000001/10.224.0.5 Sep 01,2025 11:40 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check cluster connect `echo "mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -c fe -- bash` check cluster connect done check ops status `kbcli cluster list-ops strent-mmdeab --status all --namespace ns-duzkg ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME strent-mmdeab-expose-nzfwc ns-duzkg Expose strent-mmdeab fe Running 0/1 Sep 01,2025 12:06 UTC+0800 ops_status:strent-mmdeab-expose-nzfwc ns-duzkg Expose strent-mmdeab fe Running 0/1 Sep 01,2025 12:06 UTC+0800 ops_status:strent-mmdeab-expose-nzfwc ns-duzkg Expose strent-mmdeab fe Running 0/1 Sep 01,2025 12:06 UTC+0800 ops_status:strent-mmdeab-expose-nzfwc ns-duzkg Expose strent-mmdeab fe Running 0/1 Sep 01,2025 12:06 UTC+0800 check ops status done ops_status:strent-mmdeab-expose-nzfwc ns-duzkg Expose strent-mmdeab fe Succeed 1/1 Sep 01,2025 12:06 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests strent-mmdeab-expose-nzfwc --namespace ns-duzkg ` opsrequest.apps.kubeblocks.io/strent-mmdeab-expose-nzfwc patched `kbcli cluster delete-ops --name strent-mmdeab-expose-nzfwc --force --auto-approve --namespace ns-duzkg ` OpsRequest strent-mmdeab-expose-nzfwc deleted `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys `echo "echo 'use mydb; SELECT value FROM tmp_table WHERE id = 1;' | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 -c fe --namespace ns-duzkg -- bash` check data: Unable to use a TTY - input is not a terminal or the right kind of file Warning: arning] Using a password on the command line interface can be insecure. value bkzlo check cluster data consistent Success `kubectl get secrets -l app.kubernetes.io/instance=strent-mmdeab` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.username***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.password***"` `kubectl get secrets strent-mmdeab-fe-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:8139we0aMV;DB_PORT:9030;DB_DATABASE:sys check db_client batch data count `echo "echo \"select count(*) from executions_loop.executions_loop_table;\" | mysql -P9030 -hstrent-mmdeab-fe-fe.ns-duzkg.svc.cluster.local -uroot -p'8139we0aMV' " | kubectl exec -it strent-mmdeab-fe-0 --namespace ns-duzkg -- bash ` check db_client batch data Success delete cluster strent-mmdeab `kbcli cluster delete strent-mmdeab --auto-approve --namespace ns-duzkg ` Cluster strent-mmdeab deleted pod_info:strent-mmdeab-cn-0 4/4 Running 0 23m strent-mmdeab-cn-1 4/4 Running 0 23m strent-mmdeab-fe-0 3/3 Running 0 25m strent-mmdeab-fe-1 3/3 Running 0 25m strent-mmdeab-fe-2 3/3 Running 0 26m pod_info:strent-mmdeab-cn-0 4/4 Terminating 0 23m strent-mmdeab-cn-1 4/4 Terminating 0 24m strent-mmdeab-fe-0 3/3 Running 0 25m strent-mmdeab-fe-1 3/3 Running 0 26m strent-mmdeab-fe-2 3/3 Running 0 26m No resources found in ns-duzkg namespace. delete cluster pod done No resources found in ns-duzkg namespace. check cluster resource non-exist OK: pvc No resources found in ns-duzkg namespace. delete cluster done No resources found in ns-duzkg namespace. No resources found in ns-duzkg namespace. No resources found in ns-duzkg namespace. Starrocks Ent Test Suite All Done! --------------------------------------Starrocks Ent (Topology = shared-data Replicas 2) Test Result-------------------------------------- [PASSED]|[Create]|[Topology=shared-data;ComponentVersion=starrocks-be;ServiceVersion=3.2.2;]|[Description=Create a cluster with the specified topology shared-data and component version starrocks-be and service version 3.2.2] [PASSED]|[Connect]|[ComponentName=cn]|[Description=Connect to the cluster] [PASSED]|[AddData]|[Values=bkzlo]|[Description=Add data to the cluster] [PASSED]|[Expose]|[Enable=true;TYPE=internet;ComponentName=fe]|[Description=Expose Enable the internet service with fe component] [PASSED]|[RebuildInstance]|[ComponentName=cn]|[Description=Rebuild the cluster instance specify component cn] [PASSED]|[VerticalScaling]|[ComponentName=fe]|[Description=VerticalScaling the cluster specify component fe] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [PASSED]|[Restart]|[-]|[Description=Restart the cluster] [PASSED]|[No-Failover]|[HA=Connection Stress;ComponentName=cn]|[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]|[VerticalScaling]|[ComponentName=cn]|[Description=VerticalScaling the cluster specify component cn] [PASSED]|[Restart]|[ComponentName=fe]|[Description=Restart the cluster specify component fe] [PASSED]|[HorizontalScaling Out]|[ComponentName=cn]|[Description=HorizontalScaling Out the cluster specify component cn] [PASSED]|[HorizontalScaling In]|[ComponentName=cn]|[Description=HorizontalScaling In the cluster specify component cn] [PASSED]|[Restart]|[ComponentName=cn]|[Description=Restart the cluster specify component cn] [PASSED]|[VolumeExpansion]|[ComponentName=fe]|[Description=VolumeExpansion the cluster specify component fe] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Expose]|[Disable=true;TYPE=internet;ComponentName=fe]|[Description=Expose Disable the internet service with fe component] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]