source commons files source engines files source kubeblocks files source kubedb files CLUSTER_NAME: `kubectl get namespace | grep ns-zzitr ` `kubectl create namespace ns-zzitr` namespace/ns-zzitr created create namespace ns-zzitr done download kbcli `gh release list --repo apecloud/kbcli --limit 100 | (grep "1.0" || true)` `curl -fsSL https://kubeblocks.io/installer/install_cli.sh | bash -s v1.0.1` Your system is linux_amd64 Installing kbcli ... Downloading ... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 33.6M 100 33.6M 0 0 143M 0 --:--:-- --:--:-- --:--:-- 143M kbcli installed successfully. Kubernetes: v1.32.6 KubeBlocks: 1.0.1 kbcli: 1.0.1 Make sure your docker service is running and begin your journey with kbcli: kbcli playground init For more information on how to get started, please visit: https://kubeblocks.io download kbcli v1.0.1 done Kubernetes: v1.32.6 KubeBlocks: 1.0.1 kbcli: 1.0.1 Kubernetes Env: v1.32.6 check snapshot controller check snapshot controller done POD_RESOURCES: aks kb-default-sc found aks default-vsc found found default storage class: default KubeBlocks version is:1.0.1 skip upgrade KubeBlocks current KubeBlocks version: 1.0.1 Error: no repositories to show helm repo add chaos-mesh https://charts.chaos-mesh.org "chaos-mesh" has been added to your repositories add helm chart repo chaos-mesh success chaos mesh already installed check component definition set component name:rabbitmq set component version set component version:rabbitmq set service versions:4.0.9,3.13.7,3.13.2,3.12.14,3.11.28,3.10.25,3.9.29,3.8.14 set service versions sorted:3.8.14,3.9.29,3.10.25,3.11.28,3.12.14,3.13.2,3.13.7,4.0.9 set rabbitmq component definition set rabbitmq component definition rabbitmq-1.0.1 REPORT_COUNT 0:0 set replicas first:3,3.8.14|3,3.9.29|3,3.10.25|3,3.11.28|3,3.12.14|3,3.13.2|3,3.13.7|3,4.0.9 set replicas third:3,3.11.28 set replicas fourth:3,3.11.28 set minimum cmpv service version set minimum cmpv service version replicas:3,3.11.28 REPORT_COUNT:1 CLUSTER_TOPOLOGY: set rabbitmq component definition set rabbitmq component definition rabbitmq-1.0.1 LIMIT_CPU:0.5 LIMIT_MEMORY:0.5 storage size: 1 CLUSTER_NAME:rabbitmq-apopuh No resources found in ns-zzitr namespace. pod_info: termination_policy:Delete create 3 replica Delete rabbitmq cluster check component definition set component definition by component version check cmpd by labels check cmpd by compDefs set component definition: rabbitmq-1.0.1 by component version:rabbitmq apiVersion: apps.kubeblocks.io/v1 kind: Cluster metadata: name: rabbitmq-apopuh namespace: ns-zzitr spec: clusterDef: rabbitmq topology: terminationPolicy: Delete componentSpecs: - name: rabbitmq serviceVersion: 3.11.28 replicas: 3 resources: requests: cpu: 500m memory: 0.5Gi limits: cpu: 500m memory: 0.5Gi serviceVersion: 3.11.28 volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi `kubectl apply -f test_create_rabbitmq-apopuh.yaml` cluster.apps.kubeblocks.io/rabbitmq-apopuh created apply test_create_rabbitmq-apopuh.yaml Success `rm -rf test_create_rabbitmq-apopuh.yaml` check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq Delete Creating Sep 11,2025 17:27 UTC+0800 clusterdefinition.kubeblocks.io/name=rabbitmq cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances rabbitmq-apopuh --namespace ns-zzitr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME rabbitmq-apopuh-rabbitmq-0 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:27 UTC+0800 rabbitmq-apopuh-rabbitmq-1 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:28 UTC+0800 rabbitmq-apopuh-rabbitmq-2 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:29 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check cluster connect `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 show overview " | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash` check cluster connect done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check pod rabbitmq-apopuh-rabbitmq-0 container_name rabbitmq exist password Z4E504JD2Gm8o04C check pod rabbitmq-apopuh-rabbitmq-0 container_name kbagent exist password Z4E504JD2Gm8o04C No container logs contain secret password. describe cluster `kbcli cluster describe rabbitmq-apopuh --namespace ns-zzitr ` Name: rabbitmq-apopuh Created Time: Sep 11,2025 17:27 UTC+0800 NAMESPACE CLUSTER-DEFINITION TOPOLOGY STATUS TERMINATION-POLICY ns-zzitr rabbitmq clustermode Running Delete Endpoints: COMPONENT INTERNAL EXTERNAL rabbitmq rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local:5672 rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local:15672 Topology: COMPONENT SERVICE-VERSION INSTANCE ROLE STATUS AZ NODE CREATED-TIME rabbitmq 3.11.28 rabbitmq-apopuh-rabbitmq-0 Running 0 aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:27 UTC+0800 rabbitmq 3.11.28 rabbitmq-apopuh-rabbitmq-1 Running 0 aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:28 UTC+0800 rabbitmq 3.11.28 rabbitmq-apopuh-rabbitmq-2 Running 0 aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:29 UTC+0800 Resources Allocation: COMPONENT INSTANCE-TEMPLATE CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS rabbitmq 500m / 500m 512Mi / 512Mi data:1Gi default Images: COMPONENT COMPONENT-DEFINITION IMAGE rabbitmq rabbitmq-1.0.1 docker.io/apecloud/rabbitmq:3.11.28-management Show cluster events: kbcli cluster list-events -n ns-zzitr rabbitmq-apopuh `kbcli cluster label rabbitmq-apopuh app.kubernetes.io/instance- --namespace ns-zzitr ` label "app.kubernetes.io/instance" not found. `kbcli cluster label rabbitmq-apopuh app.kubernetes.io/instance=rabbitmq-apopuh --namespace ns-zzitr ` `kbcli cluster label rabbitmq-apopuh --list --namespace ns-zzitr ` NAME NAMESPACE LABELS rabbitmq-apopuh ns-zzitr app.kubernetes.io/instance=rabbitmq-apopuh clusterdefinition.kubeblocks.io/name=rabbitmq label cluster app.kubernetes.io/instance=rabbitmq-apopuh Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=rabbitmq-apopuh --namespace ns-zzitr ` `kbcli cluster label rabbitmq-apopuh --list --namespace ns-zzitr ` NAME NAMESPACE LABELS rabbitmq-apopuh ns-zzitr app.kubernetes.io/instance=rabbitmq-apopuh case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=rabbitmq label cluster case.name=kbcli.test1 Success `kbcli cluster label rabbitmq-apopuh case.name=kbcli.test2 --overwrite --namespace ns-zzitr ` `kbcli cluster label rabbitmq-apopuh --list --namespace ns-zzitr ` NAME NAMESPACE LABELS rabbitmq-apopuh ns-zzitr app.kubernetes.io/instance=rabbitmq-apopuh case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=rabbitmq label cluster case.name=kbcli.test2 Success `kbcli cluster label rabbitmq-apopuh case.name- --namespace ns-zzitr ` `kbcli cluster label rabbitmq-apopuh --list --namespace ns-zzitr ` NAME NAMESPACE LABELS rabbitmq-apopuh ns-zzitr app.kubernetes.io/instance=rabbitmq-apopuh clusterdefinition.kubeblocks.io/name=rabbitmq delete cluster label case.name Success cluster connect `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 list nodes" | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash ` Defaulted container "rabbitmq" out of: rabbitmq, kbagent, init-kbagent (init), kbagent-worker (init) Unable to use a TTY - input is not a terminal or the right kind of file +------------------------------------------------------------------------------+------+-----------+ | name | type | mem_used | +------------------------------------------------------------------------------+------+-----------+ | rabbit@rabbitmq-apopuh-rabbitmq-0.rabbitmq-apopuh-rabbitmq-headless.ns-zzitr | disc | 158707712 | | rabbit@rabbitmq-apopuh-rabbitmq-1.rabbitmq-apopuh-rabbitmq-headless.ns-zzitr | disc | 164610048 | | rabbit@rabbitmq-apopuh-rabbitmq-2.rabbitmq-apopuh-rabbitmq-headless.ns-zzitr | disc | 163917824 | +------------------------------------------------------------------------------+------+-----------+ connect cluster Success insert batch data by db client Error from server (NotFound): pods "test-db-client-executionloop-rabbitmq-apopuh" not found `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-executionloop-rabbitmq-apopuh --namespace ns-zzitr ` Error from server (NotFound): pods "test-db-client-executionloop-rabbitmq-apopuh" 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-rabbitmq-apopuh" not found `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: apiVersion: v1 kind: Pod metadata: name: test-db-client-executionloop-rabbitmq-apopuh namespace: ns-zzitr spec: containers: - name: test-dbclient imagePullPolicy: IfNotPresent image: docker.io/apecloud/dbclient:test args: - "--host" - "rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local" - "--user" - "root" - "--password" - "Z4E504JD2Gm8o04C" - "--port" - "5672" - "--dbtype" - "rabbitmq" - "--test" - "executionloop" - "--duration" - "60" - "--interval" - "1" restartPolicy: Never `kubectl apply -f test-db-client-executionloop-rabbitmq-apopuh.yaml` pod/test-db-client-executionloop-rabbitmq-apopuh created apply test-db-client-executionloop-rabbitmq-apopuh.yaml Success `rm -rf test-db-client-executionloop-rabbitmq-apopuh.yaml` check pod status pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 5s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 10s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 15s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 20s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 25s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 30s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 35s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 40s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 46s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 51s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 56s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 61s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 66s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 71s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 76s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 82s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 87s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 92s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 97s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 102s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 107s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 113s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 118s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m3s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m8s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m13s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m18s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m23s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m29s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m34s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m39s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m44s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m49s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m54s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 2m59s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 3m5s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 3m10s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 3m15s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 3m20s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 3m25s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 3m30s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 3m36s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 3m41s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 3m46s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 3m51s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 3m56s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m1s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m6s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m12s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m17s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m22s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m27s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m32s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m37s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m42s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m48s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m53s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 4m58s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 5m3s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 5m8s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-rabbitmq-apopuh 1/1 Running 0 5m13s check pod test-db-client-executionloop-rabbitmq-apopuh status timeout --------------------------------------get pod test-db-client-executionloop-rabbitmq-apopuh yaml-------------------------------------- `kubectl get pod test-db-client-executionloop-rabbitmq-apopuh -o yaml --namespace ns-zzitr ` apiVersion: v1 kind: Pod metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | ***"apiVersion":"v1","kind":"Pod","metadata":***"annotations":***,"name":"test-db-client-executionloop-rabbitmq-apopuh","namespace":"ns-zzitr"***,"spec":***"containers":[***"args":["--host","rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local","--user","root","--password","Z4E504JD2Gm8o04C","--port","5672","--dbtype","rabbitmq","--test","executionloop","--duration","60","--interval","1"],"image":"docker.io/apecloud/dbclient:test","imagePullPolicy":"IfNotPresent","name":"test-dbclient"***],"restartPolicy":"Never"*** creationTimestamp: "2025-09-11T09:30:37Z" name: test-db-client-executionloop-rabbitmq-apopuh namespace: ns-zzitr resourceVersion: "19855" uid: 804f9889-90b4-46bf-ae87-d6d4137af521 spec: containers: - args: - --host - rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local - --user - root - --password - Z4E504JD2Gm8o04C - --port - "5672" - --dbtype - rabbitmq - --test - executionloop - --duration - "60" - --interval - "1" image: docker.io/apecloud/dbclient:test imagePullPolicy: IfNotPresent name: test-dbclient resources: *** terminationMessagePath: /dev/termination-log terminationMessagePolicy: File volumeMounts: - mountPath: /var/run/secrets/kubernetes.io/serviceaccount name: kube-api-access-7z6bf readOnly: true dnsPolicy: ClusterFirst enableServiceLinks: true nodeName: aks-cicdamdpool-12089392-vmss000003 preemptionPolicy: PreemptLowerPriority priority: 0 restartPolicy: Never schedulerName: default-scheduler securityContext: *** serviceAccount: default serviceAccountName: default terminationGracePeriodSeconds: 30 tolerations: - effect: NoExecute key: node.kubernetes.io/not-ready operator: Exists tolerationSeconds: 300 - effect: NoExecute key: node.kubernetes.io/unreachable operator: Exists tolerationSeconds: 300 volumes: - name: kube-api-access-7z6bf projected: defaultMode: 420 sources: - serviceAccountToken: expirationSeconds: 3607 path: token - configMap: items: - key: ca.crt path: ca.crt name: kube-root-ca.crt - downwardAPI: items: - fieldRef: apiVersion: v1 fieldPath: metadata.namespace path: namespace status: conditions: - lastProbeTime: null lastTransitionTime: "2025-09-11T09:30:38Z" status: "True" type: PodReadyToStartContainers - lastProbeTime: null lastTransitionTime: "2025-09-11T09:30:37Z" status: "True" type: Initialized - lastProbeTime: null lastTransitionTime: "2025-09-11T09:30:38Z" status: "True" type: Ready - lastProbeTime: null lastTransitionTime: "2025-09-11T09:30:38Z" status: "True" type: ContainersReady - lastProbeTime: null lastTransitionTime: "2025-09-11T09:30:37Z" status: "True" type: PodScheduled containerStatuses: - containerID: containerd://8d26420fb77a7eb2e1be6bddde76431e7bcd45b4fb153cdc54e203635f1e1d98 image: docker.io/apecloud/dbclient:test imageID: docker.io/apecloud/dbclient@sha256:abec5208c25fc18470ec383a06c35e29186314821be5151efcb82612aee1dcc1 lastState: *** name: test-dbclient ready: true restartCount: 0 started: true state: running: startedAt: "2025-09-11T09:30:38Z" volumeMounts: - mountPath: /var/run/secrets/kubernetes.io/serviceaccount name: kube-api-access-7z6bf readOnly: true recursiveReadOnly: Disabled hostIP: 10.224.0.8 hostIPs: - ip: 10.224.0.8 phase: Running podIP: 10.244.2.211 podIPs: - ip: 10.244.2.211 qosClass: BestEffort startTime: "2025-09-11T09:30:37Z" ------------------------------------------------------------------------------------------------------------------ --------------------------------------describe pod test-db-client-executionloop-rabbitmq-apopuh-------------------------------------- `kubectl describe pod test-db-client-executionloop-rabbitmq-apopuh --namespace ns-zzitr ` Name: test-db-client-executionloop-rabbitmq-apopuh Namespace: ns-zzitr Priority: 0 Service Account: default Node: aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Start Time: Thu, 11 Sep 2025 17:30:37 +0800 Labels: Annotations: Status: Running IP: 10.244.2.211 IPs: IP: 10.244.2.211 Containers: test-dbclient: Container ID: containerd://8d26420fb77a7eb2e1be6bddde76431e7bcd45b4fb153cdc54e203635f1e1d98 Image: docker.io/apecloud/dbclient:test Image ID: docker.io/apecloud/dbclient@sha256:abec5208c25fc18470ec383a06c35e29186314821be5151efcb82612aee1dcc1 Port: Host Port: Args: --host rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local --user root --password Z4E504JD2Gm8o04C --port 5672 --dbtype rabbitmq --test executionloop --duration 60 --interval 1 State: Running Started: Thu, 11 Sep 2025 17:30:38 +0800 Ready: True Restart Count: 0 Environment: Mounts: /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-7z6bf (ro) Conditions: Type Status PodReadyToStartContainers True Initialized True Ready True ContainersReady True PodScheduled True Volumes: kube-api-access-7z6bf: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: DownwardAPI: true QoS Class: BestEffort Node-Selectors: Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 5m14s default-scheduler Successfully assigned ns-zzitr/test-db-client-executionloop-rabbitmq-apopuh to aks-cicdamdpool-12089392-vmss000003 Normal Pulled 5m14s kubelet Container image "docker.io/apecloud/dbclient:test" already present on machine Normal Created 5m14s kubelet Created container: test-dbclient Normal Started 5m14s kubelet Started container test-dbclient ------------------------------------------------------------------------------------------------------------------ --------------------------------------pod test-db-client-executionloop-rabbitmq-apopuh-------------------------------------- `kubectl logs test-db-client-executionloop-rabbitmq-apopuh --namespace ns-zzitr --tail 500` --host rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local --user root --password Z4E504JD2Gm8o04C --port 5672 --dbtype rabbitmq --test executionloop --duration 60 --interval 1 SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider] Execution loop start: Queue executions_loop_queue created successfully. Queue executions_loop_queue deleted successfully. Queue executions_loop_queue recreated successfully. Execution loop start:***"operation":"publish","queue":"executions_loop_queue","message":"executions_loop_message_1"*** [ 1s ] executions total: 13571 successful: 13571 failed: 0 disconnect: 0 ------------------------------------------------------------------------------------------------------------------ check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq Delete Running Sep 11,2025 17:27 UTC+0800 app.kubernetes.io/instance=rabbitmq-apopuh,clusterdefinition.kubeblocks.io/name=rabbitmq check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances rabbitmq-apopuh --namespace ns-zzitr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME rabbitmq-apopuh-rabbitmq-0 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:27 UTC+0800 rabbitmq-apopuh-rabbitmq-1 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:28 UTC+0800 rabbitmq-apopuh-rabbitmq-2 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:29 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check cluster connect `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 show overview " | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash` check cluster connect done --host rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local --user root --password Z4E504JD2Gm8o04C --port 5672 --dbtype rabbitmq --test executionloop --duration 60 --interval 1 SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider] Execution loop start: Queue executions_loop_queue created successfully. Queue executions_loop_queue deleted successfully. Queue executions_loop_queue recreated successfully. Execution loop start:***"operation":"publish","queue":"executions_loop_queue","message":"executions_loop_message_1"*** [ 1s ] executions total: 13571 successful: 13571 failed: 0 disconnect: 0 DB_CLIENT_BATCH_DATA_COUNT: `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-executionloop-rabbitmq-apopuh --namespace ns-zzitr ` pod/test-db-client-executionloop-rabbitmq-apopuh 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-rabbitmq-apopuh" force deleted cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop rabbitmq-apopuh --auto-approve --force=true --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-stop-z2fkh created successfully, you can view the progress: kbcli cluster describe-ops rabbitmq-apopuh-stop-z2fkh -n ns-zzitr check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-stop-z2fkh ns-zzitr Stop rabbitmq-apopuh rabbitmq Running 0/3 Sep 11,2025 17:35 UTC+0800 check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq Delete Stopping Sep 11,2025 17:27 UTC+0800 app.kubernetes.io/instance=rabbitmq-apopuh,clusterdefinition.kubeblocks.io/name=rabbitmq cluster_status:Stopping cluster_status:Stopping check cluster status done cluster_status:Stopped check pod status `kbcli cluster list-instances rabbitmq-apopuh --namespace ns-zzitr ` 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 rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-stop-z2fkh ns-zzitr Stop rabbitmq-apopuh rabbitmq Succeed 3/3 Sep 11,2025 17:35 UTC+0800 check ops status done ops_status:rabbitmq-apopuh-stop-z2fkh ns-zzitr Stop rabbitmq-apopuh rabbitmq Succeed 3/3 Sep 11,2025 17:35 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations rabbitmq-apopuh-stop-z2fkh --namespace ns-zzitr ` opsrequest.operations.kubeblocks.io/rabbitmq-apopuh-stop-z2fkh patched `kbcli cluster delete-ops --name rabbitmq-apopuh-stop-z2fkh --force --auto-approve --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-stop-z2fkh deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start rabbitmq-apopuh --force=true --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-start-gbj2s created successfully, you can view the progress: kbcli cluster describe-ops rabbitmq-apopuh-start-gbj2s -n ns-zzitr check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-start-gbj2s ns-zzitr Start rabbitmq-apopuh rabbitmq Running 0/3 Sep 11,2025 17:36 UTC+0800 check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq Delete Updating Sep 11,2025 17:27 UTC+0800 app.kubernetes.io/instance=rabbitmq-apopuh,clusterdefinition.kubeblocks.io/name=rabbitmq cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 rabbitmq-apopuh --namespace ns-zzitr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME rabbitmq-apopuh-rabbitmq-0 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:36 UTC+0800 rabbitmq-apopuh-rabbitmq-1 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:37 UTC+0800 rabbitmq-apopuh-rabbitmq-2 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:41 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check cluster connect `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 show overview " | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash` check cluster connect done check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-start-gbj2s ns-zzitr Start rabbitmq-apopuh rabbitmq Succeed 3/3 Sep 11,2025 17:36 UTC+0800 check ops status done ops_status:rabbitmq-apopuh-start-gbj2s ns-zzitr Start rabbitmq-apopuh rabbitmq Succeed 3/3 Sep 11,2025 17:36 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations rabbitmq-apopuh-start-gbj2s --namespace ns-zzitr ` opsrequest.operations.kubeblocks.io/rabbitmq-apopuh-start-gbj2s patched `kbcli cluster delete-ops --name rabbitmq-apopuh-start-gbj2s --force --auto-approve --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-start-gbj2s deleted cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart rabbitmq-apopuh --auto-approve --force=true --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-restart-bs45m created successfully, you can view the progress: kbcli cluster describe-ops rabbitmq-apopuh-restart-bs45m -n ns-zzitr check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-restart-bs45m ns-zzitr Restart rabbitmq-apopuh rabbitmq Running 0/3 Sep 11,2025 17:43 UTC+0800 check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq Delete Updating Sep 11,2025 17:27 UTC+0800 app.kubernetes.io/instance=rabbitmq-apopuh,clusterdefinition.kubeblocks.io/name=rabbitmq 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 rabbitmq-apopuh --namespace ns-zzitr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME rabbitmq-apopuh-rabbitmq-0 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:45 UTC+0800 rabbitmq-apopuh-rabbitmq-1 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:44 UTC+0800 rabbitmq-apopuh-rabbitmq-2 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:1Gi aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:43 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check cluster connect `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 show overview " | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash` check cluster connect done check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-restart-bs45m ns-zzitr Restart rabbitmq-apopuh rabbitmq Succeed 3/3 Sep 11,2025 17:43 UTC+0800 check ops status done ops_status:rabbitmq-apopuh-restart-bs45m ns-zzitr Restart rabbitmq-apopuh rabbitmq Succeed 3/3 Sep 11,2025 17:43 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations rabbitmq-apopuh-restart-bs45m --namespace ns-zzitr ` opsrequest.operations.kubeblocks.io/rabbitmq-apopuh-restart-bs45m patched `kbcli cluster delete-ops --name rabbitmq-apopuh-restart-bs45m --force --auto-approve --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-restart-bs45m deleted `kubectl get pvc -l app.kubernetes.io/instance=rabbitmq-apopuh,apps.kubeblocks.io/component-name=rabbitmq,apps.kubeblocks.io/vct-name=data --namespace ns-zzitr ` cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in rabbitmq-apopuh namespace. `kbcli cluster volume-expand rabbitmq-apopuh --auto-approve --force=true --components rabbitmq --volume-claim-templates data --storage 2Gi --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-volumeexpansion-rhb5z created successfully, you can view the progress: kbcli cluster describe-ops rabbitmq-apopuh-volumeexpansion-rhb5z -n ns-zzitr check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-volumeexpansion-rhb5z ns-zzitr VolumeExpansion rabbitmq-apopuh rabbitmq Running 0/3 Sep 11,2025 17:46 UTC+0800 check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq Delete Updating Sep 11,2025 17:27 UTC+0800 app.kubernetes.io/instance=rabbitmq-apopuh,clusterdefinition.kubeblocks.io/name=rabbitmq cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 rabbitmq-apopuh --namespace ns-zzitr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME rabbitmq-apopuh-rabbitmq-0 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:2Gi aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:45 UTC+0800 rabbitmq-apopuh-rabbitmq-1 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:2Gi aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:44 UTC+0800 rabbitmq-apopuh-rabbitmq-2 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:2Gi aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:43 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check cluster connect `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 show overview " | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash` check cluster connect done No resources found in rabbitmq-apopuh namespace. check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-volumeexpansion-rhb5z ns-zzitr VolumeExpansion rabbitmq-apopuh rabbitmq Succeed 3/3 Sep 11,2025 17:46 UTC+0800 check ops status done ops_status:rabbitmq-apopuh-volumeexpansion-rhb5z ns-zzitr VolumeExpansion rabbitmq-apopuh rabbitmq Succeed 3/3 Sep 11,2025 17:46 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations rabbitmq-apopuh-volumeexpansion-rhb5z --namespace ns-zzitr ` opsrequest.operations.kubeblocks.io/rabbitmq-apopuh-volumeexpansion-rhb5z patched `kbcli cluster delete-ops --name rabbitmq-apopuh-volumeexpansion-rhb5z --force --auto-approve --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-volumeexpansion-rhb5z deleted test failover connectionstress check cluster status before cluster-failover-connectionstress check cluster status done cluster_status:Running Error from server (NotFound): pods "test-db-client-connectionstress-rabbitmq-apopuh" not found `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-connectionstress-rabbitmq-apopuh --namespace ns-zzitr ` Error from server (NotFound): pods "test-db-client-connectionstress-rabbitmq-apopuh" 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-rabbitmq-apopuh" not found `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: apiVersion: v1 kind: Pod metadata: name: test-db-client-connectionstress-rabbitmq-apopuh namespace: ns-zzitr spec: containers: - name: test-dbclient imagePullPolicy: IfNotPresent image: docker.io/apecloud/dbclient:test args: - "--host" - "rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local" - "--user" - "root" - "--password" - "Z4E504JD2Gm8o04C" - "--port" - "5672" - "--database" - "" - "--dbtype" - "rabbitmq" - "--test" - "connectionstress" - "--connections" - "5000" - "--duration" - "60" restartPolicy: Never `kubectl apply -f test-db-client-connectionstress-rabbitmq-apopuh.yaml` pod/test-db-client-connectionstress-rabbitmq-apopuh created apply test-db-client-connectionstress-rabbitmq-apopuh.yaml Success `rm -rf test-db-client-connectionstress-rabbitmq-apopuh.yaml` check pod status pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-rabbitmq-apopuh 1/1 Running 0 5s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-rabbitmq-apopuh 1/1 Running 0 26s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-rabbitmq-apopuh 1/1 Running 0 51s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-rabbitmq-apopuh 1/1 Running 0 76s check pod test-db-client-connectionstress-rabbitmq-apopuh status done pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-rabbitmq-apopuh 0/1 Completed 0 101s check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq Delete Running Sep 11,2025 17:27 UTC+0800 app.kubernetes.io/instance=rabbitmq-apopuh,clusterdefinition.kubeblocks.io/name=rabbitmq check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances rabbitmq-apopuh --namespace ns-zzitr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME rabbitmq-apopuh-rabbitmq-0 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:2Gi aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:45 UTC+0800 rabbitmq-apopuh-rabbitmq-1 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:2Gi aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:44 UTC+0800 rabbitmq-apopuh-rabbitmq-2 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 500m / 500m 512Mi / 512Mi data:2Gi aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:43 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check cluster connect `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 show overview " | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash` check cluster connect done --host rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local --user root --password Z4E504JD2Gm8o04C --port 5672 --database --dbtype rabbitmq --test connectionstress --connections 5000 --duration 60 SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider] Test Result: Connection stress test results: Duration: 60 seconds Successful connections: 5000 Failed connections: 0 Connection Information: Database Type: rabbitmq Host: rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local Port: 5672 Database: Table: User: root Org: Access Mode: mysql Test Type: connectionstress Connection Count: 5000 Duration: 60 seconds `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-connectionstress-rabbitmq-apopuh --namespace ns-zzitr ` pod/test-db-client-connectionstress-rabbitmq-apopuh 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-rabbitmq-apopuh" force deleted check failover pod name failover pod name:rabbitmq-apopuh-rabbitmq-0 failover connectionstress Success check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale rabbitmq-apopuh --auto-approve --force=true --components rabbitmq --cpu 600m --memory 0.6Gi --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-verticalscaling-rmhnn created successfully, you can view the progress: kbcli cluster describe-ops rabbitmq-apopuh-verticalscaling-rmhnn -n ns-zzitr check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-verticalscaling-rmhnn ns-zzitr VerticalScaling rabbitmq-apopuh rabbitmq Running 0/3 Sep 11,2025 17:54 UTC+0800 check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq Delete Updating Sep 11,2025 17:27 UTC+0800 app.kubernetes.io/instance=rabbitmq-apopuh,clusterdefinition.kubeblocks.io/name=rabbitmq 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 rabbitmq-apopuh --namespace ns-zzitr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME rabbitmq-apopuh-rabbitmq-0 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:57 UTC+0800 rabbitmq-apopuh-rabbitmq-1 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:55 UTC+0800 rabbitmq-apopuh-rabbitmq-2 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:55 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check cluster connect `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 show overview " | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash` check cluster connect done check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-verticalscaling-rmhnn ns-zzitr VerticalScaling rabbitmq-apopuh rabbitmq Succeed 3/3 Sep 11,2025 17:54 UTC+0800 check ops status done ops_status:rabbitmq-apopuh-verticalscaling-rmhnn ns-zzitr VerticalScaling rabbitmq-apopuh rabbitmq Succeed 3/3 Sep 11,2025 17:54 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations rabbitmq-apopuh-verticalscaling-rmhnn --namespace ns-zzitr ` opsrequest.operations.kubeblocks.io/rabbitmq-apopuh-verticalscaling-rmhnn patched `kbcli cluster delete-ops --name rabbitmq-apopuh-verticalscaling-rmhnn --force --auto-approve --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-verticalscaling-rmhnn deleted cluster does not need to check monitor currently check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq Delete Running Sep 11,2025 17:27 UTC+0800 app.kubernetes.io/instance=rabbitmq-apopuh,clusterdefinition.kubeblocks.io/name=rabbitmq check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances rabbitmq-apopuh --namespace ns-zzitr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME rabbitmq-apopuh-rabbitmq-0 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:57 UTC+0800 rabbitmq-apopuh-rabbitmq-1 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:55 UTC+0800 rabbitmq-apopuh-rabbitmq-2 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:55 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check cluster connect `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 show overview " | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash` check cluster connect done cluster rabbitmq scale-out cluster rabbitmq scale-out replicas: 4 check cluster status before ops check cluster status done cluster_status:Running No resources found in rabbitmq-apopuh namespace. `kbcli cluster scale-out rabbitmq-apopuh --auto-approve --force=true --components rabbitmq --replicas 1 --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-horizontalscaling-c4kc8 created successfully, you can view the progress: kbcli cluster describe-ops rabbitmq-apopuh-horizontalscaling-c4kc8 -n ns-zzitr check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-horizontalscaling-c4kc8 ns-zzitr HorizontalScaling rabbitmq-apopuh rabbitmq Running 0/1 Sep 11,2025 17:57 UTC+0800 check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq Delete Updating Sep 11,2025 17:27 UTC+0800 app.kubernetes.io/instance=rabbitmq-apopuh,clusterdefinition.kubeblocks.io/name=rabbitmq cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances rabbitmq-apopuh --namespace ns-zzitr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME rabbitmq-apopuh-rabbitmq-0 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:57 UTC+0800 rabbitmq-apopuh-rabbitmq-1 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:55 UTC+0800 rabbitmq-apopuh-rabbitmq-2 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:55 UTC+0800 rabbitmq-apopuh-rabbitmq-3 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-default-50058069-vmss000000/10.224.0.4 Sep 11,2025 17:57 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check cluster connect `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 show overview " | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash` check cluster connect done No resources found in rabbitmq-apopuh namespace. check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-horizontalscaling-c4kc8 ns-zzitr HorizontalScaling rabbitmq-apopuh rabbitmq Succeed 1/1 Sep 11,2025 17:57 UTC+0800 check ops status done ops_status:rabbitmq-apopuh-horizontalscaling-c4kc8 ns-zzitr HorizontalScaling rabbitmq-apopuh rabbitmq Succeed 1/1 Sep 11,2025 17:57 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations rabbitmq-apopuh-horizontalscaling-c4kc8 --namespace ns-zzitr ` opsrequest.operations.kubeblocks.io/rabbitmq-apopuh-horizontalscaling-c4kc8 patched `kbcli cluster delete-ops --name rabbitmq-apopuh-horizontalscaling-c4kc8 --force --auto-approve --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-horizontalscaling-c4kc8 deleted cluster rabbitmq scale-in cluster rabbitmq scale-in replicas: 3 check cluster status before ops check cluster status done cluster_status:Running No resources found in rabbitmq-apopuh namespace. `kbcli cluster scale-in rabbitmq-apopuh --auto-approve --force=true --components rabbitmq --replicas 1 --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-horizontalscaling-v9w9l created successfully, you can view the progress: kbcli cluster describe-ops rabbitmq-apopuh-horizontalscaling-v9w9l -n ns-zzitr check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-horizontalscaling-v9w9l ns-zzitr HorizontalScaling rabbitmq-apopuh rabbitmq Running -/- Sep 11,2025 17:59 UTC+0800 check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq Delete Updating Sep 11,2025 17:27 UTC+0800 app.kubernetes.io/instance=rabbitmq-apopuh,clusterdefinition.kubeblocks.io/name=rabbitmq check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances rabbitmq-apopuh --namespace ns-zzitr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME rabbitmq-apopuh-rabbitmq-0 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:57 UTC+0800 rabbitmq-apopuh-rabbitmq-1 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:55 UTC+0800 rabbitmq-apopuh-rabbitmq-2 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:55 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check cluster connect `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 show overview " | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash` check cluster connect done No resources found in rabbitmq-apopuh namespace. check ops status `kbcli cluster list-ops rabbitmq-apopuh --status all --namespace ns-zzitr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME rabbitmq-apopuh-horizontalscaling-v9w9l ns-zzitr HorizontalScaling rabbitmq-apopuh rabbitmq Succeed 1/1 Sep 11,2025 17:59 UTC+0800 check ops status done ops_status:rabbitmq-apopuh-horizontalscaling-v9w9l ns-zzitr HorizontalScaling rabbitmq-apopuh rabbitmq Succeed 1/1 Sep 11,2025 17:59 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations rabbitmq-apopuh-horizontalscaling-v9w9l --namespace ns-zzitr ` opsrequest.operations.kubeblocks.io/rabbitmq-apopuh-horizontalscaling-v9w9l patched `kbcli cluster delete-ops --name rabbitmq-apopuh-horizontalscaling-v9w9l --force --auto-approve --namespace ns-zzitr ` OpsRequest rabbitmq-apopuh-horizontalscaling-v9w9l deleted cluster update terminationPolicy WipeOut `kbcli cluster update rabbitmq-apopuh --termination-policy=WipeOut --namespace ns-zzitr ` cluster.apps.kubeblocks.io/rabbitmq-apopuh updated check cluster status `kbcli cluster list rabbitmq-apopuh --show-labels --namespace ns-zzitr ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS rabbitmq-apopuh ns-zzitr rabbitmq WipeOut Running Sep 11,2025 17:27 UTC+0800 app.kubernetes.io/instance=rabbitmq-apopuh,clusterdefinition.kubeblocks.io/name=rabbitmq check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances rabbitmq-apopuh --namespace ns-zzitr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME rabbitmq-apopuh-rabbitmq-0 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000000/10.224.0.5 Sep 11,2025 17:57 UTC+0800 rabbitmq-apopuh-rabbitmq-1 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000003/10.224.0.8 Sep 11,2025 17:55 UTC+0800 rabbitmq-apopuh-rabbitmq-2 ns-zzitr rabbitmq-apopuh rabbitmq Running 0 600m / 600m 644245094400m / 644245094400m data:2Gi aks-cicdamdpool-12089392-vmss000001/10.224.0.7 Sep 11,2025 17:55 UTC+0800 check pod status done `kubectl get secrets -l app.kubernetes.io/instance=rabbitmq-apopuh` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.username***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.password***"` `kubectl get secrets rabbitmq-apopuh-rabbitmq-account-root -o jsonpath="***.data.port***"` DB_USERNAME:root;DB_PASSWORD:Z4E504JD2Gm8o04C;DB_PORT:15672;DB_DATABASE: check cluster connect `echo "rabbitmqadmin -H rabbitmq-apopuh-rabbitmq.ns-zzitr.svc.cluster.local -u root -p 'Z4E504JD2Gm8o04C' -P 15672 show overview " | kubectl exec -it rabbitmq-apopuh-rabbitmq-0 --namespace ns-zzitr -- bash` check cluster connect done cluster list-logs `kbcli cluster list-logs rabbitmq-apopuh --namespace ns-zzitr ` No log files found. Error from server (NotFound): pods "rabbitmq-apopuh-rabbitmq-0" not found cluster logs `kbcli cluster logs rabbitmq-apopuh --tail 30 --namespace ns-zzitr ` Defaulted container "rabbitmq" out of: rabbitmq, kbagent, init-kbagent (init), kbagent-worker (init) Notice: 11 09:57:27.331870+00:00 [notice] <0.44.0> Application syslog exited with reason: stopped Notice: 11 09:57:27.337301+00:00 [notice] <0.240.0> Logging: switching to configured handler(s); following messages may not be visible in this log output ## ## RabbitMQ 3.11.28 ## ## ########## Copyright (c) 2007-2023 Broadcom Inc and/or its subsidiaries ###### ## ########## Licensed under the MPL 2.0. Website: https://rabbitmq.com Erlang: 25.3.2.9 [jit] TLS Library: OpenSSL - OpenSSL 3.1.5 30 Jan 2024 Release series support status: supported Doc guides: https://rabbitmq.com/documentation.html Support: https://rabbitmq.com/contact.html Tutorials: https://rabbitmq.com/getstarted.html Monitoring: https://rabbitmq.com/monitoring.html Logs: /var/lib/rabbitmq/log/rabbit.log /var/lib/rabbitmq/logs/rabbit@rabbitmq-apopuh-rabbitmq-0.rabbitmq-apopuh-rabbitmq-headless.ns-zzitr_upgrade.log Config file(s): /etc/rabbitmq/conf.d/10-defaults.conf /etc/rabbitmq/conf.d/12-kubeblocks.conf Starting broker... completed with 4 plugins. delete cluster rabbitmq-apopuh `kbcli cluster delete rabbitmq-apopuh --auto-approve --namespace ns-zzitr ` Cluster rabbitmq-apopuh deleted pod_info:rabbitmq-apopuh-rabbitmq-0 2/2 Running 0 2m40s rabbitmq-apopuh-rabbitmq-1 2/2 Running 0 3m50s rabbitmq-apopuh-rabbitmq-2 2/2 Running 1 (4m26s ago) 4m44s pod_info:rabbitmq-apopuh-rabbitmq-0 2/2 Terminating 0 3m rabbitmq-apopuh-rabbitmq-1 2/2 Terminating 0 4m10s No resources found in ns-zzitr namespace. delete cluster pod done No resources found in ns-zzitr namespace. check cluster resource non-exist OK: pvc No resources found in ns-zzitr namespace. delete cluster done No resources found in ns-zzitr namespace. No resources found in ns-zzitr namespace. No resources found in ns-zzitr namespace. Rabbitmq Test Suite All Done! Test Engine: rabbitmq Test Type: 53 --------------------------------------Rabbitmq (Topology = Replicas 3) Test Result-------------------------------------- [PASSED]|[Create]|[ComponentDefinition=rabbitmq-1.0.1;ComponentVersion=rabbitmq;ServiceVersion=3.11.28;]|[Description=Create a cluster with the specified component definition rabbitmq-1.0.1 and component version rabbitmq and service version 3.11.28] [PASSED]|[Connect]|[ComponentName=rabbitmq]|[Description=Connect to the cluster] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [PASSED]|[Restart]|[-]|[Description=Restart the cluster] [PASSED]|[VolumeExpansion]|[ComponentName=rabbitmq]|[Description=VolumeExpansion the cluster specify component rabbitmq] [PASSED]|[No-Failover]|[HA=Connection Stress;ComponentName=rabbitmq]|[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=rabbitmq]|[Description=VerticalScaling the cluster specify component rabbitmq] [PASSED]|[Update]|[Monitor=true]|[Description=Update the cluster Monitor enable] [PASSED]|[HorizontalScaling Out]|[ComponentName=rabbitmq]|[Description=HorizontalScaling Out the cluster specify component rabbitmq] [PASSED]|[HorizontalScaling In]|[ComponentName=rabbitmq]|[Description=HorizontalScaling In the cluster specify component rabbitmq] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]