source commons files source engines files source kubeblocks files source kubedb files CLUSTER_NAME: `kubectl get namespace | grep ns-qyyor ` `kubectl create namespace ns-qyyor` namespace/ns-qyyor created create namespace ns-qyyor 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 63.9M 0 --:--:-- --:--:-- --:--:-- 63.9M 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:postgresql set component version set component version:vanilla-postgresql set service versions:15.7.0,14.7.0,12.15.0 set service versions sorted:12.15.0,14.7.0,15.7.0 set vanilla-postgresql component definition set vanilla-postgresql component definition vanilla-postgresql-15-1.0.1 REPORT_COUNT 0:0 set replicas first:2,12.15.0|2,14.7.0|2,15.7.0 set replicas third:2,12.15.0 set replicas fourth:2,12.15.0 set minimum cmpv service version set minimum cmpv service version replicas:2,12.15.0 REPORT_COUNT:1 CLUSTER_TOPOLOGY: set vanilla-postgresql component definition set vanilla-postgresql component definition vanilla-postgresql-15-1.0.1 LIMIT_CPU:0.5 LIMIT_MEMORY:0.5 storage size: 3 CLUSTER_NAME:vanilla-ekesge No resources found in ns-qyyor namespace. pod_info: termination_policy:WipeOut create 2 replica WipeOut vanilla-postgresql cluster check component definition set component definition by component version check cmpd by labels set component definition1: vanilla-postgresql-12-1.0.1 by component version:vanilla-postgresql apiVersion: apps.kubeblocks.io/v1 kind: Cluster metadata: name: vanilla-ekesge namespace: ns-qyyor spec: clusterDef: vanilla-postgresql topology: terminationPolicy: WipeOut componentSpecs: - name: postgresql serviceVersion: 12.15.0 replicas: 2 disableExporter: true resources: requests: cpu: 500m memory: 0.5Gi limits: cpu: 500m memory: 0.5Gi volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 3Gi `kubectl apply -f test_create_vanilla-ekesge.yaml` cluster.apps.kubeblocks.io/vanilla-ekesge created apply test_create_vanilla-ekesge.yaml Success `rm -rf test_create_vanilla-ekesge.yaml` check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Creating Sep 11,2025 17:20 UTC+0800 clusterdefinition.kubeblocks.io/name=vanilla-postgresql 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 vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:21 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:22 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done `kubectl get secrets -l app.kubernetes.io/instance=vanilla-ekesge` `kubectl get secrets vanilla-ekesge-postgresql-account-postgres -o jsonpath="***.data.username***"` `kubectl get secrets vanilla-ekesge-postgresql-account-postgres -o jsonpath="***.data.password***"` `kubectl get secrets vanilla-ekesge-postgresql-account-postgres -o jsonpath="***.data.port***"` DB_USERNAME:postgres;DB_PASSWORD:d9GX245U8N;DB_PORT:5432;DB_DATABASE: check pod vanilla-ekesge-postgresql-0 container_name postgresql exist password d9GX245U8N check pod vanilla-ekesge-postgresql-0 container_name kbagent exist password d9GX245U8N check pod vanilla-ekesge-postgresql-0 container_name config-manager exist password d9GX245U8N No container logs contain secret password. describe cluster `kbcli cluster describe vanilla-ekesge --namespace ns-qyyor ` Name: vanilla-ekesge Created Time: Sep 11,2025 17:20 UTC+0800 NAMESPACE CLUSTER-DEFINITION TOPOLOGY STATUS TERMINATION-POLICY ns-qyyor vanilla-postgresql vanilla-postgresql Running WipeOut Endpoints: COMPONENT INTERNAL EXTERNAL postgresql vanilla-ekesge-postgresql.ns-qyyor.svc.cluster.local:5432 Topology: COMPONENT SERVICE-VERSION INSTANCE ROLE STATUS AZ NODE CREATED-TIME postgresql 12.15.0 vanilla-ekesge-postgresql-0 primary Running 0 aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:21 UTC+0800 postgresql 12.15.0 vanilla-ekesge-postgresql-1 secondary Running 0 aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:22 UTC+0800 Resources Allocation: COMPONENT INSTANCE-TEMPLATE CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS postgresql 500m / 500m 512Mi / 512Mi data:3Gi default Images: COMPONENT COMPONENT-DEFINITION IMAGE postgresql vanilla-postgresql-12-1.0.1 docker.io/apecloud/postgres:12.15 docker.io/apecloud/kubeblocks-tools:1.0.1 Data Protection: BACKUP-REPO AUTO-BACKUP BACKUP-SCHEDULE BACKUP-METHOD BACKUP-RETENTION RECOVERABLE-TIME Show cluster events: kbcli cluster list-events -n ns-qyyor vanilla-ekesge `kbcli cluster label vanilla-ekesge app.kubernetes.io/instance- --namespace ns-qyyor ` label "app.kubernetes.io/instance" not found. `kbcli cluster label vanilla-ekesge app.kubernetes.io/instance=vanilla-ekesge --namespace ns-qyyor ` `kbcli cluster label vanilla-ekesge --list --namespace ns-qyyor ` NAME NAMESPACE LABELS vanilla-ekesge ns-qyyor app.kubernetes.io/instance=vanilla-ekesge clusterdefinition.kubeblocks.io/name=vanilla-postgresql label cluster app.kubernetes.io/instance=vanilla-ekesge Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=vanilla-ekesge --namespace ns-qyyor ` `kbcli cluster label vanilla-ekesge --list --namespace ns-qyyor ` NAME NAMESPACE LABELS vanilla-ekesge ns-qyyor app.kubernetes.io/instance=vanilla-ekesge case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=vanilla-postgresql label cluster case.name=kbcli.test1 Success `kbcli cluster label vanilla-ekesge case.name=kbcli.test2 --overwrite --namespace ns-qyyor ` `kbcli cluster label vanilla-ekesge --list --namespace ns-qyyor ` NAME NAMESPACE LABELS vanilla-ekesge ns-qyyor app.kubernetes.io/instance=vanilla-ekesge case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=vanilla-postgresql label cluster case.name=kbcli.test2 Success `kbcli cluster label vanilla-ekesge case.name- --namespace ns-qyyor ` `kbcli cluster label vanilla-ekesge --list --namespace ns-qyyor ` NAME NAMESPACE LABELS vanilla-ekesge ns-qyyor app.kubernetes.io/instance=vanilla-ekesge clusterdefinition.kubeblocks.io/name=vanilla-postgresql delete cluster label case.name Success cluster connect `echo 'select 1' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres ` Defaulted container "postgresql" out of: postgresql, kbagent, config-manager, init-syncer (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file ?column? ---------- 1 (1 row) connect cluster Success LB_TYPE is set to: intranet cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose vanilla-ekesge --auto-approve --force=true --type intranet --enable true --components postgresql --role-selector primary --namespace ns-qyyor ` OpsRequest vanilla-ekesge-expose-nvc5d created successfully, you can view the progress: kbcli cluster describe-ops vanilla-ekesge-expose-nvc5d -n ns-qyyor check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:21 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:22 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 17:23 UTC+0800 check ops status done ops_status:vanilla-ekesge-expose-nvc5d ns-qyyor Expose vanilla-ekesge postgresql Succeed 1/1 Sep 11,2025 17:23 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vanilla-ekesge-expose-nvc5d --namespace ns-qyyor ` opsrequest.operations.kubeblocks.io/vanilla-ekesge-expose-nvc5d patched `kbcli cluster delete-ops --name vanilla-ekesge-expose-nvc5d --force --auto-approve --namespace ns-qyyor ` OpsRequest vanilla-ekesge-expose-nvc5d deleted 11 test failover dnserror check cluster status before cluster-failover-dnserror check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnserror-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): dnschaos.chaos-mesh.org "test-chaos-mesh-dnserror-vanilla-ekesge" not found Error from server (NotFound): dnschaos.chaos-mesh.org "test-chaos-mesh-dnserror-vanilla-ekesge" not found apiVersion: chaos-mesh.org/v1alpha1 kind: DNSChaos metadata: name: test-chaos-mesh-dnserror-vanilla-ekesge namespace: ns-qyyor spec: selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-0 mode: all action: error duration: 2m `kubectl apply -f test-chaos-mesh-dnserror-vanilla-ekesge.yaml` dnschaos.chaos-mesh.org/test-chaos-mesh-dnserror-vanilla-ekesge created apply test-chaos-mesh-dnserror-vanilla-ekesge.yaml Success `rm -rf test-chaos-mesh-dnserror-vanilla-ekesge.yaml` dnserror chaos test waiting 120 seconds check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:21 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:22 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnserror-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. dnschaos.chaos-mesh.org "test-chaos-mesh-dnserror-vanilla-ekesge" force deleted Error from server (NotFound): dnschaos.chaos-mesh.org "test-chaos-mesh-dnserror-vanilla-ekesge" not found check failover pod name failover pod name:vanilla-ekesge-postgresql-0 failover dnserror Success test failover networkpartition check cluster status before cluster-failover-networkpartition check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkpartition-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkpartition-vanilla-ekesge" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkpartition-vanilla-ekesge" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkpartition-vanilla-ekesge namespace: ns-qyyor spec: selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-0 action: partition mode: all target: mode: all selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-1 direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkpartition-vanilla-ekesge.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkpartition-vanilla-ekesge created apply test-chaos-mesh-networkpartition-vanilla-ekesge.yaml Success `rm -rf test-chaos-mesh-networkpartition-vanilla-ekesge.yaml` networkpartition chaos test waiting 120 seconds check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:21 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:22 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` connect checking... check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkpartition-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. networkchaos.chaos-mesh.org "test-chaos-mesh-networkpartition-vanilla-ekesge" force deleted Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkpartition-vanilla-ekesge" not found check failover pod name failover pod name:vanilla-ekesge-postgresql-0 failover networkpartition Success test failover dnsrandom check cluster status before cluster-failover-dnsrandom check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnsrandom-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): dnschaos.chaos-mesh.org "test-chaos-mesh-dnsrandom-vanilla-ekesge" not found Error from server (NotFound): dnschaos.chaos-mesh.org "test-chaos-mesh-dnsrandom-vanilla-ekesge" not found apiVersion: chaos-mesh.org/v1alpha1 kind: DNSChaos metadata: name: test-chaos-mesh-dnsrandom-vanilla-ekesge namespace: ns-qyyor spec: selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-0 mode: all action: random duration: 2m `kubectl apply -f test-chaos-mesh-dnsrandom-vanilla-ekesge.yaml` Error from server (InternalError): error when creating "test-chaos-mesh-dnsrandom-vanilla-ekesge.yaml": Internal error occurred: failed calling webhook "mdnschaos.kb.io": failed to call webhook: Post "https://chaos-mesh-controller-manager.chaos-mesh.svc:443/mutate-chaos-mesh-org-v1alpha1-dnschaos?timeout=5s": EOF apply test-chaos-mesh-dnsrandom-vanilla-ekesge.yaml retry Error from server (InternalError): error when creating "test-chaos-mesh-dnsrandom-vanilla-ekesge.yaml": Internal error occurred: failed calling webhook "mdnschaos.kb.io": failed to call webhook: Post "https://chaos-mesh-controller-manager.chaos-mesh.svc:443/mutate-chaos-mesh-org-v1alpha1-dnschaos?timeout=5s": EOF apply test-chaos-mesh-dnsrandom-vanilla-ekesge.yaml retry dnschaos.chaos-mesh.org/test-chaos-mesh-dnsrandom-vanilla-ekesge created apply test-chaos-mesh-dnsrandom-vanilla-ekesge.yaml Success `rm -rf test-chaos-mesh-dnsrandom-vanilla-ekesge.yaml` dnsrandom chaos test waiting 120 seconds check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:21 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:22 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnsrandom-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. dnschaos.chaos-mesh.org "test-chaos-mesh-dnsrandom-vanilla-ekesge" force deleted dnschaos.chaos-mesh.org/test-chaos-mesh-dnsrandom-vanilla-ekesge patched check failover pod name failover pod name:vanilla-ekesge-postgresql-0 failover dnsrandom Success cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop vanilla-ekesge --auto-approve --force=true --namespace ns-qyyor ` OpsRequest vanilla-ekesge-stop-zlgbm created successfully, you can view the progress: kbcli cluster describe-ops vanilla-ekesge-stop-zlgbm -n ns-qyyor check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-stop-zlgbm ns-qyyor Stop vanilla-ekesge postgresql Running 0/2 Sep 11,2025 17:32 UTC+0800 check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Stopped Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Stopped check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` 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 vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-stop-zlgbm ns-qyyor Stop vanilla-ekesge postgresql Succeed 2/2 Sep 11,2025 17:32 UTC+0800 check ops status done ops_status:vanilla-ekesge-stop-zlgbm ns-qyyor Stop vanilla-ekesge postgresql Succeed 2/2 Sep 11,2025 17:32 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vanilla-ekesge-stop-zlgbm --namespace ns-qyyor ` opsrequest.operations.kubeblocks.io/vanilla-ekesge-stop-zlgbm patched `kbcli cluster delete-ops --name vanilla-ekesge-stop-zlgbm --force --auto-approve --namespace ns-qyyor ` OpsRequest vanilla-ekesge-stop-zlgbm deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start vanilla-ekesge --force=true --namespace ns-qyyor ` OpsRequest vanilla-ekesge-start-xn66n created successfully, you can view the progress: kbcli cluster describe-ops vanilla-ekesge-start-xn66n -n ns-qyyor check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-start-xn66n ns-qyyor Start vanilla-ekesge postgresql Running 0/2 Sep 11,2025 17:33 UTC+0800 check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Updating Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:33 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 500m / 500m 512Mi / 512Mi data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:44 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-start-xn66n ns-qyyor Start vanilla-ekesge postgresql Succeed 2/2 Sep 11,2025 17:33 UTC+0800 check ops status done ops_status:vanilla-ekesge-start-xn66n ns-qyyor Start vanilla-ekesge postgresql Succeed 2/2 Sep 11,2025 17:33 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vanilla-ekesge-start-xn66n --namespace ns-qyyor ` opsrequest.operations.kubeblocks.io/vanilla-ekesge-start-xn66n patched `kbcli cluster delete-ops --name vanilla-ekesge-start-xn66n --force --auto-approve --namespace ns-qyyor ` OpsRequest vanilla-ekesge-start-xn66n deleted check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale vanilla-ekesge --auto-approve --force=true --components postgresql --cpu 600m --memory 0.6Gi --namespace ns-qyyor ` OpsRequest vanilla-ekesge-verticalscaling-mkxt7 created successfully, you can view the progress: kbcli cluster describe-ops vanilla-ekesge-verticalscaling-mkxt7 -n ns-qyyor check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-verticalscaling-mkxt7 ns-qyyor VerticalScaling vanilla-ekesge postgresql Running 0/2 Sep 11,2025 17:46 UTC+0800 check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Updating Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql 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 vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:46 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:46 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-1;secondary: vanilla-ekesge-postgresql-0 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-1 --namespace ns-qyyor -- psql -U postgres` check cluster connect done check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-verticalscaling-mkxt7 ns-qyyor VerticalScaling vanilla-ekesge postgresql Failed 2/2 Sep 11,2025 17:46 UTC+0800 check ops status done check opsrequest progress ops_status:vanilla-ekesge-verticalscaling-mkxt7 ns-qyyor VerticalScaling vanilla-ekesge postgresql Failed 2/2 Sep 11,2025 17:46 UTC+0800 --------------------------------------get cluster vanilla-ekesge yaml-------------------------------------- `kubectl get cluster vanilla-ekesge -o yaml --namespace ns-qyyor ` apiVersion: apps.kubeblocks.io/v1 kind: Cluster metadata: annotations: kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1 kubectl.kubernetes.io/last-applied-configuration: | ***"apiVersion":"apps.kubeblocks.io/v1","kind":"Cluster","metadata":***"annotations":***,"name":"vanilla-ekesge","namespace":"ns-qyyor"***,"spec":***"clusterDef":"vanilla-postgresql","componentSpecs":[***"disableExporter":true,"name":"postgresql","replicas":2,"resources":***"limits":***"cpu":"500m","memory":"0.5Gi"***,"requests":***"cpu":"500m","memory":"0.5Gi"***,"serviceVersion":"12.15.0","volumeClaimTemplates":[***"name":"data","spec":***"accessModes":["ReadWriteOnce"],"resources":***"requests":***"storage":"3Gi"***,"storageClassName":null***]***],"terminationPolicy":"WipeOut","topology":null*** creationTimestamp: "2025-09-11T09:20:57Z" finalizers: - cluster.kubeblocks.io/finalizer generation: 7 labels: app.kubernetes.io/instance: vanilla-ekesge clusterdefinition.kubeblocks.io/name: vanilla-postgresql name: vanilla-ekesge namespace: ns-qyyor resourceVersion: "42240" uid: 3db3b5c2-6d88-404c-9ac5-4b81d53e092f spec: clusterDef: vanilla-postgresql componentSpecs: - componentDef: vanilla-postgresql-12-1.0.1 disableExporter: true name: postgresql replicas: 2 resources: limits: cpu: 600m memory: 644245094400m requests: cpu: 600m memory: 644245094400m serviceVersion: 12.15.0 volumeClaimTemplates: - name: data spec: accessModes: - ReadWriteOnce resources: requests: storage: 3Gi services: - annotations: service.beta.kubernetes.io/azure-load-balancer-internal: "true" componentSelector: postgresql name: postgresql-intranet roleSelector: primary serviceName: postgresql-intranet spec: ports: - name: tcp-postgresql nodePort: 32001 port: 5432 protocol: TCP targetPort: tcp-postgresql type: LoadBalancer terminationPolicy: WipeOut topology: vanilla-postgresql status: components: postgresql: message: InstanceSet/vanilla-ekesge-postgresql: '["vanilla-ekesge-postgresql-0"]' observedGeneration: 7 phase: Running upToDate: true conditions: - lastTransitionTime: "2025-09-11T09:20:57Z" message: 'The operator has started the provisioning of Cluster: vanilla-ekesge' observedGeneration: 7 reason: PreCheckSucceed status: "True" type: ProvisioningStarted - lastTransitionTime: "2025-09-11T09:20:57Z" message: Successfully applied for resources observedGeneration: 7 reason: ApplyResourcesSucceed status: "True" type: ApplyResources - lastTransitionTime: "2025-09-11T09:46:51Z" message: cluster vanilla-ekesge is ready reason: ClusterReady status: "True" type: Ready observedGeneration: 7 phase: Running ------------------------------------------------------------------------------------------------------------------ --------------------------------------describe cluster vanilla-ekesge-------------------------------------- `kubectl describe cluster vanilla-ekesge --namespace ns-qyyor ` Name: vanilla-ekesge Namespace: ns-qyyor Labels: app.kubernetes.io/instance=vanilla-ekesge clusterdefinition.kubeblocks.io/name=vanilla-postgresql Annotations: kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1 API Version: apps.kubeblocks.io/v1 Kind: Cluster Metadata: Creation Timestamp: 2025-09-11T09:20:57Z Finalizers: cluster.kubeblocks.io/finalizer Generation: 7 Resource Version: 42240 UID: 3db3b5c2-6d88-404c-9ac5-4b81d53e092f Spec: Cluster Def: vanilla-postgresql Component Specs: Component Def: vanilla-postgresql-12-1.0.1 Disable Exporter: true Name: postgresql Replicas: 2 Resources: Limits: Cpu: 600m Memory: 644245094400m Requests: Cpu: 600m Memory: 644245094400m Service Version: 12.15.0 Volume Claim Templates: Name: data Spec: Access Modes: ReadWriteOnce Resources: Requests: Storage: 3Gi Services: Annotations: service.beta.kubernetes.io/azure-load-balancer-internal: true Component Selector: postgresql Name: postgresql-intranet Role Selector: primary Service Name: postgresql-intranet Spec: Ports: Name: tcp-postgresql Node Port: 32001 Port: 5432 Protocol: TCP Target Port: tcp-postgresql Type: LoadBalancer Termination Policy: WipeOut Topology: vanilla-postgresql Status: Components: Postgresql: Message: InstanceSet/vanilla-ekesge-postgresql: ["vanilla-ekesge-postgresql-0"] Observed Generation: 7 Phase: Running Up To Date: true Conditions: Last Transition Time: 2025-09-11T09:20:57Z Message: The operator has started the provisioning of Cluster: vanilla-ekesge Observed Generation: 7 Reason: PreCheckSucceed Status: True Type: ProvisioningStarted Last Transition Time: 2025-09-11T09:20:57Z Message: Successfully applied for resources Observed Generation: 7 Reason: ApplyResourcesSucceed Status: True Type: ApplyResources Last Transition Time: 2025-09-11T09:46:51Z Message: cluster vanilla-ekesge is ready Reason: ClusterReady Status: True Type: Ready Observed Generation: 7 Phase: Running Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal ClusterComponentPhaseTransition 25m (x2 over 25m) cluster-controller cluster component postgresql is Creating Normal ClusterReady 23m cluster-controller cluster vanilla-ekesge is ready Normal PreCheckSucceed 23m (x4 over 26m) cluster-controller The operator has started the provisioning of Cluster: vanilla-ekesge Normal ApplyResourcesSucceed 23m (x4 over 26m) cluster-controller Successfully applied for resources Normal Running 72s (x2 over 23m) cluster-controller Cluster: vanilla-ekesge is ready, current phase is Running Normal ClusterComponentPhaseTransition 41s (x27 over 23m) cluster-controller cluster component postgresql is Running ------------------------------------------------------------------------------------------------------------------ --------------------------------------get opsrequests.operations vanilla-ekesge-verticalscaling-mkxt7 yaml-------------------------------------- `kubectl get opsrequests.operations vanilla-ekesge-verticalscaling-mkxt7 -o yaml --namespace ns-qyyor ` apiVersion: operations.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: creationTimestamp: "2025-09-11T09:46:17Z" finalizers: - opsrequest.kubeblocks.io/finalizer generateName: vanilla-ekesge-verticalscaling- generation: 2 labels: app.kubernetes.io/instance: vanilla-ekesge app.kubernetes.io/managed-by: kubeblocks operations.kubeblocks.io/ops-type: VerticalScaling name: vanilla-ekesge-verticalscaling-mkxt7 namespace: ns-qyyor ownerReferences: - apiVersion: apps.kubeblocks.io/v1 kind: Cluster name: vanilla-ekesge uid: 3db3b5c2-6d88-404c-9ac5-4b81d53e092f resourceVersion: "42189" uid: 61e487c5-96fd-4743-acea-5457978790a2 spec: clusterName: vanilla-ekesge enqueueOnForce: false force: true preConditionDeadlineSeconds: 0 type: VerticalScaling verticalScaling: - componentName: postgresql limits: cpu: 600m memory: 644245094400m requests: cpu: 600m memory: 644245094400m status: clusterGeneration: 7 completionTimestamp: "2025-09-11T09:46:50Z" components: postgresql: phase: Failed progressDetails: - endTime: "2025-09-11T09:46:50Z" message: 'Failed to vertical scale: Pod/vanilla-ekesge-postgresql-0 in Component: postgresql, message: ' objectKey: Pod/vanilla-ekesge-postgresql-0 startTime: "2025-09-11T09:46:38Z" status: Failed - endTime: "2025-09-11T09:46:38Z" message: 'Successfully vertical scale: Pod/vanilla-ekesge-postgresql-1 in Component: postgresql' objectKey: Pod/vanilla-ekesge-postgresql-1 startTime: "2025-09-11T09:46:17Z" status: Succeed conditions: - lastTransitionTime: "2025-09-11T09:46:17Z" message: 'wait for the controller to process the OpsRequest: vanilla-ekesge-verticalscaling-mkxt7 in Cluster: vanilla-ekesge' reason: WaitForProgressing status: "True" type: WaitForProgressing - lastTransitionTime: "2025-09-11T09:46:17Z" message: 'OpsRequest: vanilla-ekesge-verticalscaling-mkxt7 is validated' reason: ValidateOpsRequestPassed status: "True" type: Validated - lastTransitionTime: "2025-09-11T09:46:17Z" message: 'Start to vertical scale resources in Cluster: vanilla-ekesge' reason: VerticalScalingStarted status: "True" type: VerticalScaling - lastTransitionTime: "2025-09-11T09:46:50Z" message: 'Failed to process OpsRequest: vanilla-ekesge-verticalscaling-mkxt7 in cluster: vanilla-ekesge, more detailed informations in status.components' reason: OpsRequestFailed status: "False" type: Failed lastConfiguration: components: postgresql: limits: cpu: 500m memory: 512Mi requests: cpu: 500m memory: 512Mi phase: Failed progress: 2/2 startTimestamp: "2025-09-11T09:46:17Z" ------------------------------------------------------------------------------------------------------------------ --------------------------------------describe opsrequests.operations vanilla-ekesge-verticalscaling-mkxt7-------------------------------------- `kubectl describe opsrequests.operations vanilla-ekesge-verticalscaling-mkxt7 --namespace ns-qyyor ` Name: vanilla-ekesge-verticalscaling-mkxt7 Namespace: ns-qyyor Labels: app.kubernetes.io/instance=vanilla-ekesge app.kubernetes.io/managed-by=kubeblocks operations.kubeblocks.io/ops-type=VerticalScaling Annotations: API Version: operations.kubeblocks.io/v1alpha1 Kind: OpsRequest Metadata: Creation Timestamp: 2025-09-11T09:46:17Z Finalizers: opsrequest.kubeblocks.io/finalizer Generate Name: vanilla-ekesge-verticalscaling- Generation: 2 Owner References: API Version: apps.kubeblocks.io/v1 Kind: Cluster Name: vanilla-ekesge UID: 3db3b5c2-6d88-404c-9ac5-4b81d53e092f Resource Version: 42189 UID: 61e487c5-96fd-4743-acea-5457978790a2 Spec: Cluster Name: vanilla-ekesge Enqueue On Force: false Force: true Pre Condition Deadline Seconds: 0 Type: VerticalScaling Vertical Scaling: Component Name: postgresql Limits: Cpu: 600m Memory: 644245094400m Requests: Cpu: 600m Memory: 644245094400m Status: Cluster Generation: 7 Completion Timestamp: 2025-09-11T09:46:50Z Components: Postgresql: Phase: Failed Progress Details: End Time: 2025-09-11T09:46:50Z Message: Failed to vertical scale: Pod/vanilla-ekesge-postgresql-0 in Component: postgresql, message: Object Key: Pod/vanilla-ekesge-postgresql-0 Start Time: 2025-09-11T09:46:38Z Status: Failed End Time: 2025-09-11T09:46:38Z Message: Successfully vertical scale: Pod/vanilla-ekesge-postgresql-1 in Component: postgresql Object Key: Pod/vanilla-ekesge-postgresql-1 Start Time: 2025-09-11T09:46:17Z Status: Succeed Conditions: Last Transition Time: 2025-09-11T09:46:17Z Message: wait for the controller to process the OpsRequest: vanilla-ekesge-verticalscaling-mkxt7 in Cluster: vanilla-ekesge Reason: WaitForProgressing Status: True Type: WaitForProgressing Last Transition Time: 2025-09-11T09:46:17Z Message: OpsRequest: vanilla-ekesge-verticalscaling-mkxt7 is validated Reason: ValidateOpsRequestPassed Status: True Type: Validated Last Transition Time: 2025-09-11T09:46:17Z Message: Start to vertical scale resources in Cluster: vanilla-ekesge Reason: VerticalScalingStarted Status: True Type: VerticalScaling Last Transition Time: 2025-09-11T09:46:50Z Message: Failed to process OpsRequest: vanilla-ekesge-verticalscaling-mkxt7 in cluster: vanilla-ekesge, more detailed informations in status.components Reason: OpsRequestFailed Status: False Type: Failed Last Configuration: Components: Postgresql: Limits: Cpu: 500m Memory: 512Mi Requests: Cpu: 500m Memory: 512Mi Phase: Failed Progress: 2/2 Start Timestamp: 2025-09-11T09:46:17Z Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal WaitForProgressing 42s ops-request-controller wait for the controller to process the OpsRequest: vanilla-ekesge-verticalscaling-mkxt7 in Cluster: vanilla-ekesge Normal ValidateOpsRequestPassed 42s (x2 over 42s) ops-request-controller OpsRequest: vanilla-ekesge-verticalscaling-mkxt7 is validated Normal VerticalScalingStarted 42s (x2 over 42s) ops-request-controller Start to vertical scale resources in Cluster: vanilla-ekesge Normal Processing 42s ops-request-controller Start to vertical scale: Pod/vanilla-ekesge-postgresql-1 in Component: postgresql Normal Processing 21s ops-request-controller Start to vertical scale: Pod/vanilla-ekesge-postgresql-0 in Component: postgresql Normal Succeed 21s ops-request-controller Successfully vertical scale: Pod/vanilla-ekesge-postgresql-1 in Component: postgresql Warning Failed 9s ops-request-controller Failed to vertical scale: Pod/vanilla-ekesge-postgresql-0 in Component: postgresql, message: Warning OpsRequestFailed 9s ops-request-controller Failed to process OpsRequest: vanilla-ekesge-verticalscaling-mkxt7 in cluster: vanilla-ekesge, more detailed informations in status.components ------------------------------------------------------------------------------------------------------------------ `kubectl get jobs -l ops.kubeblocks.io/ops-name=vanilla-ekesge-verticalscaling-mkxt7 --namespace ns-qyyor` No resources found in ns-qyyor namespace. `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vanilla-ekesge-verticalscaling-mkxt7 --namespace ns-qyyor ` opsrequest.operations.kubeblocks.io/vanilla-ekesge-verticalscaling-mkxt7 patched `kbcli cluster delete-ops --name vanilla-ekesge-verticalscaling-mkxt7 --force --auto-approve --namespace ns-qyyor ` OpsRequest vanilla-ekesge-verticalscaling-mkxt7 deleted test failover networkcorruptover check cluster status before cluster-failover-networkcorruptover check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkcorruptover-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkcorruptover-vanilla-ekesge" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkcorruptover-vanilla-ekesge" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkcorruptover-vanilla-ekesge namespace: ns-qyyor spec: selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-1 mode: all action: corrupt corrupt: corrupt: '100' correlation: '100' direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkcorruptover-vanilla-ekesge.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkcorruptover-vanilla-ekesge created apply test-chaos-mesh-networkcorruptover-vanilla-ekesge.yaml Success `rm -rf test-chaos-mesh-networkcorruptover-vanilla-ekesge.yaml` networkcorruptover chaos test waiting 120 seconds check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:46 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:46 UTC+0800 check pod status done check cluster role No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: No resources found in ns-qyyor namespace. primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: primary: vanilla-ekesge-postgresql-0 vanilla-ekesge-postgresql-1;secondary: vanilla-ekesge-postgresql-1 check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkcorruptover-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. networkchaos.chaos-mesh.org "test-chaos-mesh-networkcorruptover-vanilla-ekesge" force deleted Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkcorruptover-vanilla-ekesge" not found check failover pod name failover pod name:vanilla-ekesge-postgresql-0 failover networkcorruptover Success test failover fullcpu check cluster status before cluster-failover-fullcpu check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-fullcpu-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-fullcpu-vanilla-ekesge" not found Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-fullcpu-vanilla-ekesge" not found apiVersion: chaos-mesh.org/v1alpha1 kind: StressChaos metadata: name: test-chaos-mesh-fullcpu-vanilla-ekesge namespace: ns-qyyor spec: selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-0 mode: all stressors: cpu: workers: 100 load: 100 duration: 2m `kubectl apply -f test-chaos-mesh-fullcpu-vanilla-ekesge.yaml` stresschaos.chaos-mesh.org/test-chaos-mesh-fullcpu-vanilla-ekesge created apply test-chaos-mesh-fullcpu-vanilla-ekesge.yaml Success `rm -rf test-chaos-mesh-fullcpu-vanilla-ekesge.yaml` fullcpu chaos test waiting 120 seconds check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:46 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:46 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-fullcpu-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. stresschaos.chaos-mesh.org "test-chaos-mesh-fullcpu-vanilla-ekesge" force deleted Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-fullcpu-vanilla-ekesge" not found check failover pod name failover pod name:vanilla-ekesge-postgresql-0 failover fullcpu Success test failover networkduplicate check cluster status before cluster-failover-networkduplicate check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkduplicate-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkduplicate-vanilla-ekesge" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkduplicate-vanilla-ekesge" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkduplicate-vanilla-ekesge namespace: ns-qyyor spec: selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-0 mode: all action: duplicate duplicate: duplicate: '100' correlation: '100' direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkduplicate-vanilla-ekesge.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkduplicate-vanilla-ekesge created apply test-chaos-mesh-networkduplicate-vanilla-ekesge.yaml Success `rm -rf test-chaos-mesh-networkduplicate-vanilla-ekesge.yaml` networkduplicate chaos test waiting 120 seconds check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:46 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:46 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkduplicate-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. networkchaos.chaos-mesh.org "test-chaos-mesh-networkduplicate-vanilla-ekesge" force deleted Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkduplicate-vanilla-ekesge" not found check failover pod name failover pod name:vanilla-ekesge-postgresql-0 failover networkduplicate Success skip Reconfiguring: `kubectl get secrets -l app.kubernetes.io/instance=vanilla-ekesge` `kubectl get secrets vanilla-ekesge-postgresql-account-postgres -o jsonpath="***.data.username***"` `kubectl get secrets vanilla-ekesge-postgresql-account-postgres -o jsonpath="***.data.password***"` `kubectl get secrets vanilla-ekesge-postgresql-account-postgres -o jsonpath="***.data.port***"` DB_USERNAME:postgres;DB_PASSWORD:d9GX245U8N;DB_PORT:5432;DB_DATABASE: `create database benchtest;` Defaulted container "postgresql" out of: postgresql, kbagent, config-manager, init-syncer (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file NOTICE: database "benchtest" does not exist, skipping return msg:DROP DATABASE CREATE DATABASE apiVersion: v1 kind: Pod metadata: name: benchtest-vanilla-ekesge namespace: ns-qyyor spec: containers: - name: test-sysbench imagePullPolicy: IfNotPresent image: docker.io/apecloud/customsuites:latest env: - name: TYPE value: "2" - name: FLAG value: "0" - name: CONFIGS value: "mode:all,driver:pgsql,host:vanilla-ekesge-postgresql.ns-qyyor.svc.cluster.local,user:postgres,password:d9GX245U8N,port:5432,db:benchtest,tables:5,threads:4,times:10,size:1000,type:oltp_read_write" restartPolicy: Never `kubectl apply -f benchtest-vanilla-ekesge.yaml` pod/benchtest-vanilla-ekesge created apply benchtest-vanilla-ekesge.yaml Success check pod status pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 0/1 ContainerCreating 0 1s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 0/1 ContainerCreating 0 5s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 0/1 ContainerCreating 0 10s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 0/1 ContainerCreating 0 15s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 1/1 Running 0 20s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 1/1 Running 0 26s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 1/1 Running 0 31s check pod benchtest-vanilla-ekesge status done pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 0/1 Completed 0 36s `rm -rf benchtest-vanilla-ekesge.yaml` `kubectl logs benchtest-vanilla-ekesge --tail 30 --namespace ns-qyyor ` [ 7s ] thds: 4 tps: 388.92 qps: 7849.32 (r/w/o: 5499.83/1559.67/789.83) lat (ms,99%): 73.13 err/s: 4.00 reconn/s: 0.00 [ 8s ] thds: 4 tps: 405.08 qps: 8120.61 (r/w/o: 5684.13/1620.32/816.16) lat (ms,99%): 73.13 err/s: 1.00 reconn/s: 0.00 [ 9s ] thds: 4 tps: 388.01 qps: 7853.24 (r/w/o: 5502.17/1560.05/791.02) lat (ms,99%): 73.13 err/s: 6.00 reconn/s: 0.00 [ 10s ] thds: 4 tps: 386.00 qps: 7712.94 (r/w/o: 5398.96/1540.99/772.99) lat (ms,99%): 75.82 err/s: 0.00 reconn/s: 0.00 SQL statistics: queries performed: read: 51870 write: 14743 other: 7439 total: 74052 transactions: 3681 (365.82 per sec.) queries: 74052 (7359.36 per sec.) ignored errors: 24 (2.39 per sec.) reconnects: 0 (0.00 per sec.) General statistics: total time: 10.0606s total number of events: 3681 Latency (ms): min: 2.41 avg: 10.93 max: 86.35 99th percentile: 75.82 sum: 40223.64 Threads fairness: events (avg/stddev): 920.2500/32.51 execution time (avg/stddev): 10.0559/0.00 `kubectl delete pod benchtest-vanilla-ekesge --force --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. pod "benchtest-vanilla-ekesge" force deleted LB_TYPE is set to: intranet No resources found in ns-qyyor namespace. `kubectl get secrets -l app.kubernetes.io/instance=vanilla-ekesge` `kubectl get secrets vanilla-ekesge-postgresql-account-postgres -o jsonpath="***.data.username***"` `kubectl get secrets vanilla-ekesge-postgresql-account-postgres -o jsonpath="***.data.password***"` `kubectl get secrets vanilla-ekesge-postgresql-account-postgres -o jsonpath="***.data.port***"` DB_USERNAME:postgres;DB_PASSWORD:d9GX245U8N;DB_PORT:5432;DB_DATABASE: `create database benchtest;` Defaulted container "postgresql" out of: postgresql, kbagent, config-manager, init-syncer (init), kbagent-worker (init), install-config-manager-tool (init) Unable to use a TTY - input is not a terminal or the right kind of file return msg:DROP DATABASE CREATE DATABASE apiVersion: v1 kind: Pod metadata: name: benchtest-vanilla-ekesge namespace: ns-qyyor spec: containers: - name: test-sysbench imagePullPolicy: IfNotPresent image: docker.io/apecloud/customsuites:latest env: - name: TYPE value: "2" - name: FLAG value: "0" - name: CONFIGS value: "mode:all,driver:pgsql,host:10.224.0.7,user:postgres,password:d9GX245U8N,port:5432,db:benchtest,tables:5,threads:4,times:10,size:1000,type:oltp_read_write" restartPolicy: Never `kubectl apply -f benchtest-vanilla-ekesge.yaml` pod/benchtest-vanilla-ekesge created apply benchtest-vanilla-ekesge.yaml Success check pod status pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 0/1 ContainerCreating 0 0s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 1/1 Running 0 4s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 1/1 Running 0 10s check pod benchtest-vanilla-ekesge status done pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-ekesge 0/1 Completed 0 15s `rm -rf benchtest-vanilla-ekesge.yaml` `kubectl logs benchtest-vanilla-ekesge --tail 30 --namespace ns-qyyor ` [ 7s ] thds: 4 tps: 388.07 qps: 7769.38 (r/w/o: 5437.97/1551.28/780.14) lat (ms,99%): 73.13 err/s: 1.00 reconn/s: 0.00 [ 8s ] thds: 4 tps: 345.01 qps: 6902.16 (r/w/o: 4829.11/1381.03/692.02) lat (ms,99%): 80.03 err/s: 0.00 reconn/s: 0.00 [ 9s ] thds: 4 tps: 397.91 qps: 7933.29 (r/w/o: 5549.80/1586.66/796.83) lat (ms,99%): 71.83 err/s: 0.00 reconn/s: 0.00 [ 10s ] thds: 4 tps: 255.00 qps: 5140.01 (r/w/o: 3607.01/1021.00/512.00) lat (ms,99%): 71.83 err/s: 0.00 reconn/s: 0.00 SQL statistics: queries performed: read: 47320 write: 13463 other: 6785 total: 67568 transactions: 3366 (316.83 per sec.) queries: 67568 (6359.92 per sec.) ignored errors: 14 (1.32 per sec.) reconnects: 0 (0.00 per sec.) General statistics: total time: 10.6224s total number of events: 3366 Latency (ms): min: 2.41 avg: 12.62 max: 1007.83 99th percentile: 75.82 sum: 42470.01 Threads fairness: events (avg/stddev): 841.5000/41.55 execution time (avg/stddev): 10.6175/0.00 `kubectl delete pod benchtest-vanilla-ekesge --force --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. pod "benchtest-vanilla-ekesge" force deleted test failover timeoffset check cluster status before cluster-failover-timeoffset check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge TimeChaos test-chaos-mesh-timeoffset-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): timechaos.chaos-mesh.org "test-chaos-mesh-timeoffset-vanilla-ekesge" not found Error from server (NotFound): timechaos.chaos-mesh.org "test-chaos-mesh-timeoffset-vanilla-ekesge" not found apiVersion: chaos-mesh.org/v1alpha1 kind: TimeChaos metadata: name: test-chaos-mesh-timeoffset-vanilla-ekesge namespace: ns-qyyor spec: selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-0 mode: all timeOffset: '-10m' clockIds: - CLOCK_REALTIME duration: 2m `kubectl apply -f test-chaos-mesh-timeoffset-vanilla-ekesge.yaml` timechaos.chaos-mesh.org/test-chaos-mesh-timeoffset-vanilla-ekesge created apply test-chaos-mesh-timeoffset-vanilla-ekesge.yaml Success `rm -rf test-chaos-mesh-timeoffset-vanilla-ekesge.yaml` timeoffset chaos test waiting 120 seconds check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:46 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:46 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge TimeChaos test-chaos-mesh-timeoffset-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. timechaos.chaos-mesh.org "test-chaos-mesh-timeoffset-vanilla-ekesge" force deleted Error from server (NotFound): timechaos.chaos-mesh.org "test-chaos-mesh-timeoffset-vanilla-ekesge" not found check failover pod name failover pod name:vanilla-ekesge-postgresql-0 failover timeoffset Success test failover networklossover check cluster status before cluster-failover-networklossover check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networklossover-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networklossover-vanilla-ekesge" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networklossover-vanilla-ekesge" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networklossover-vanilla-ekesge namespace: ns-qyyor spec: selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-0 mode: all action: loss loss: loss: '100' correlation: '100' direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networklossover-vanilla-ekesge.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networklossover-vanilla-ekesge created apply test-chaos-mesh-networklossover-vanilla-ekesge.yaml Success `rm -rf test-chaos-mesh-networklossover-vanilla-ekesge.yaml` networklossover chaos test waiting 120 seconds check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Error primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 17:46 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 17:46 UTC+0800 pod_status:Error pod_status:Error pod_status:Error check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-1;secondary: vanilla-ekesge-postgresql-0 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-1 --namespace ns-qyyor -- psql -U postgres` check cluster connect done 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. `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networklossover-vanilla-ekesge --namespace ns-qyyor ` networkchaos.chaos-mesh.org "test-chaos-mesh-networklossover-vanilla-ekesge" force deleted Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networklossover-vanilla-ekesge" not found check failover pod name failover pod name:vanilla-ekesge-postgresql-1 failover networklossover Success cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart vanilla-ekesge --auto-approve --force=true --namespace ns-qyyor ` OpsRequest vanilla-ekesge-restart-wblc4 created successfully, you can view the progress: kbcli cluster describe-ops vanilla-ekesge-restart-wblc4 -n ns-qyyor check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-restart-wblc4 ns-qyyor Restart vanilla-ekesge postgresql Running 0/2 Sep 11,2025 18:01 UTC+0800 check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Updating Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql 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 vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 18:01 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 18:01 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-restart-wblc4 ns-qyyor Restart vanilla-ekesge postgresql Succeed 2/2 Sep 11,2025 18:01 UTC+0800 check ops status done ops_status:vanilla-ekesge-restart-wblc4 ns-qyyor Restart vanilla-ekesge postgresql Succeed 2/2 Sep 11,2025 18:01 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vanilla-ekesge-restart-wblc4 --namespace ns-qyyor ` opsrequest.operations.kubeblocks.io/vanilla-ekesge-restart-wblc4 patched `kbcli cluster delete-ops --name vanilla-ekesge-restart-wblc4 --force --auto-approve --namespace ns-qyyor ` OpsRequest vanilla-ekesge-restart-wblc4 deleted test failover podfailure check cluster status before cluster-failover-podfailure check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge PodChaos test-chaos-mesh-podfailure-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podfailure-vanilla-ekesge" not found Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podfailure-vanilla-ekesge" not found apiVersion: chaos-mesh.org/v1alpha1 kind: PodChaos metadata: name: test-chaos-mesh-podfailure-vanilla-ekesge namespace: ns-qyyor spec: selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-0 mode: all action: pod-failure duration: 2m `kubectl apply -f test-chaos-mesh-podfailure-vanilla-ekesge.yaml` podchaos.chaos-mesh.org/test-chaos-mesh-podfailure-vanilla-ekesge created apply test-chaos-mesh-podfailure-vanilla-ekesge.yaml Success `rm -rf test-chaos-mesh-podfailure-vanilla-ekesge.yaml` podfailure chaos test waiting 120 seconds check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Failed Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql cluster_status:Failed cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 18:01 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 18:01 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-1;secondary: vanilla-ekesge-postgresql-0 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-1 --namespace ns-qyyor -- psql -U postgres` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge PodChaos test-chaos-mesh-podfailure-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. podchaos.chaos-mesh.org "test-chaos-mesh-podfailure-vanilla-ekesge" force deleted Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podfailure-vanilla-ekesge" not found check failover pod name failover pod name:vanilla-ekesge-postgresql-1 failover podfailure Success test failover oom check cluster status before cluster-failover-oom check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-oom-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-oom-vanilla-ekesge" not found Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-oom-vanilla-ekesge" not found apiVersion: chaos-mesh.org/v1alpha1 kind: StressChaos metadata: name: test-chaos-mesh-oom-vanilla-ekesge namespace: ns-qyyor spec: selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-1 mode: all stressors: memory: workers: 1 size: "100GB" oomScoreAdj: -1000 duration: 2m `kubectl apply -f test-chaos-mesh-oom-vanilla-ekesge.yaml` stresschaos.chaos-mesh.org/test-chaos-mesh-oom-vanilla-ekesge created apply test-chaos-mesh-oom-vanilla-ekesge.yaml Success `rm -rf test-chaos-mesh-oom-vanilla-ekesge.yaml` check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 18:01 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 18:01 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-oom-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. stresschaos.chaos-mesh.org "test-chaos-mesh-oom-vanilla-ekesge" force deleted stresschaos.chaos-mesh.org/test-chaos-mesh-oom-vanilla-ekesge patched check failover pod name failover pod name:vanilla-ekesge-postgresql-0 failover oom Success skip Reconfiguring: test failover networkdelay check cluster status before cluster-failover-networkdelay check cluster status done cluster_status:Running `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkdelay-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkdelay-vanilla-ekesge" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkdelay-vanilla-ekesge" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkdelay-vanilla-ekesge namespace: ns-qyyor spec: selector: namespaces: - ns-qyyor labelSelectors: apps.kubeblocks.io/pod-name: vanilla-ekesge-postgresql-0 mode: all action: delay delay: latency: 2000ms correlation: '100' jitter: 0ms direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkdelay-vanilla-ekesge.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkdelay-vanilla-ekesge created apply test-chaos-mesh-networkdelay-vanilla-ekesge.yaml Success `rm -rf test-chaos-mesh-networkdelay-vanilla-ekesge.yaml` networkdelay chaos test waiting 120 seconds check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 18:01 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 18:01 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkdelay-vanilla-ekesge --namespace ns-qyyor ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. networkchaos.chaos-mesh.org "test-chaos-mesh-networkdelay-vanilla-ekesge" force deleted Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkdelay-vanilla-ekesge" not found check failover pod name failover pod name:vanilla-ekesge-postgresql-0 failover networkdelay Success cluster postgresql scale-out cluster postgresql scale-out replicas: 3 check cluster status before ops check cluster status done cluster_status:Running No resources found in vanilla-ekesge namespace. `kbcli cluster scale-out vanilla-ekesge --auto-approve --force=true --components postgresql --replicas 1 --namespace ns-qyyor ` OpsRequest vanilla-ekesge-horizontalscaling-cv9js created successfully, you can view the progress: kbcli cluster describe-ops vanilla-ekesge-horizontalscaling-cv9js -n ns-qyyor check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-horizontalscaling-cv9js ns-qyyor HorizontalScaling vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:06 UTC+0800 check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Updating Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql 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 vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 18:01 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 18:01 UTC+0800 vanilla-ekesge-postgresql-2 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000002/10.224.0.9 Sep 11,2025 18:06 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 vanilla-ekesge-postgresql-2 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done No resources found in vanilla-ekesge namespace. check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-horizontalscaling-cv9js ns-qyyor HorizontalScaling vanilla-ekesge postgresql Succeed 1/1 Sep 11,2025 18:06 UTC+0800 check ops status done ops_status:vanilla-ekesge-horizontalscaling-cv9js ns-qyyor HorizontalScaling vanilla-ekesge postgresql Succeed 1/1 Sep 11,2025 18:06 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vanilla-ekesge-horizontalscaling-cv9js --namespace ns-qyyor ` opsrequest.operations.kubeblocks.io/vanilla-ekesge-horizontalscaling-cv9js patched `kbcli cluster delete-ops --name vanilla-ekesge-horizontalscaling-cv9js --force --auto-approve --namespace ns-qyyor ` OpsRequest vanilla-ekesge-horizontalscaling-cv9js deleted cluster postgresql scale-in cluster postgresql scale-in replicas: 2 check cluster status before ops check cluster status done cluster_status:Running No resources found in vanilla-ekesge namespace. `kbcli cluster scale-in vanilla-ekesge --auto-approve --force=true --components postgresql --replicas 1 --namespace ns-qyyor ` OpsRequest vanilla-ekesge-horizontalscaling-4brsp created successfully, you can view the progress: kbcli cluster describe-ops vanilla-ekesge-horizontalscaling-4brsp -n ns-qyyor check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-horizontalscaling-4brsp ns-qyyor HorizontalScaling vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:07 UTC+0800 check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 18:01 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 18:01 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done No resources found in vanilla-ekesge namespace. check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-horizontalscaling-4brsp ns-qyyor HorizontalScaling vanilla-ekesge postgresql Succeed 1/1 Sep 11,2025 18:07 UTC+0800 check ops status done ops_status:vanilla-ekesge-horizontalscaling-4brsp ns-qyyor HorizontalScaling vanilla-ekesge postgresql Succeed 1/1 Sep 11,2025 18:07 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vanilla-ekesge-horizontalscaling-4brsp --namespace ns-qyyor ` opsrequest.operations.kubeblocks.io/vanilla-ekesge-horizontalscaling-4brsp patched `kbcli cluster delete-ops --name vanilla-ekesge-horizontalscaling-4brsp --force --auto-approve --namespace ns-qyyor ` OpsRequest vanilla-ekesge-horizontalscaling-4brsp deleted `kubectl get pvc -l app.kubernetes.io/instance=vanilla-ekesge,apps.kubeblocks.io/component-name=postgresql,apps.kubeblocks.io/vct-name=data --namespace ns-qyyor ` cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in vanilla-ekesge namespace. `kbcli cluster volume-expand vanilla-ekesge --auto-approve --force=true --components postgresql --volume-claim-templates data --storage 4Gi --namespace ns-qyyor ` OpsRequest vanilla-ekesge-volumeexpansion-lnv2m created successfully, you can view the progress: kbcli cluster describe-ops vanilla-ekesge-volumeexpansion-lnv2m -n ns-qyyor check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-volumeexpansion-lnv2m ns-qyyor VolumeExpansion vanilla-ekesge postgresql Running 0/2 Sep 11,2025 18:08 UTC+0800 check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Updating Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 18:01 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 18:01 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done No resources found in vanilla-ekesge namespace. check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-volumeexpansion-lnv2m ns-qyyor VolumeExpansion vanilla-ekesge postgresql Succeed 2/2 Sep 11,2025 18:08 UTC+0800 check ops status done ops_status:vanilla-ekesge-volumeexpansion-lnv2m ns-qyyor VolumeExpansion vanilla-ekesge postgresql Succeed 2/2 Sep 11,2025 18:08 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vanilla-ekesge-volumeexpansion-lnv2m --namespace ns-qyyor ` opsrequest.operations.kubeblocks.io/vanilla-ekesge-volumeexpansion-lnv2m patched `kbcli cluster delete-ops --name vanilla-ekesge-volumeexpansion-lnv2m --force --auto-approve --namespace ns-qyyor ` OpsRequest vanilla-ekesge-volumeexpansion-lnv2m deleted cluster update terminationPolicy WipeOut `kbcli cluster update vanilla-ekesge --termination-policy=WipeOut --namespace ns-qyyor ` cluster.apps.kubeblocks.io/vanilla-ekesge updated (no change) check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 18:01 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 18:01 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done cluster list-logs `kbcli cluster list-logs vanilla-ekesge --namespace ns-qyyor ` No log files found. Error from server (NotFound): pods "vanilla-ekesge-postgresql-0" not found cluster logs `kbcli cluster logs vanilla-ekesge --tail 30 --namespace ns-qyyor ` Defaulted container "postgresql" out of: postgresql, kbagent, config-manager, init-syncer (init), kbagent-worker (init), install-config-manager-tool (init) 2025-09-11T10:04:12Z INFO PostgreSQL no action coz i still follow the leader:vanilla-ekesge-postgresql-1 2025-09-11T10:04:40Z INFO DCS-K8S lock expired: map[acquire-time:1757584928 available-time:1757585064 dbstate:***"OpTimestamp":134250936,"Extra":***"replication_mode":"off","timeline":"7"*** extra: holder:vanilla-ekesge-postgresql-1 leader:vanilla-ekesge-postgresql-1 renew-time:1757585064 ttl:15], now: 1757585080 2025-09-11T10:04:40Z INFO DCS-K8S lock expired: map[acquire-time:1757584928 available-time:1757585064 dbstate:***"OpTimestamp":134250936,"Extra":***"replication_mode":"off","timeline":"7"*** extra: holder:vanilla-ekesge-postgresql-1 leader:vanilla-ekesge-postgresql-1 renew-time:1757585064 ttl:15], now: 1757585080 2025-09-11T10:04:40Z INFO HA Cluster has no leader, attempt to take the leader 2025-09-11T10:04:40Z INFO HA Failover happens, i am the healthiest member, attempt to take the leader 2025-09-11T10:04:40Z INFO event send event: map[member:vanilla-ekesge-postgresql-0 message:Failover happens, i am the healthiest member, attempt to take the leader operation:healthyCheck] 2025-09-11T10:04:41Z INFO PostgreSQL promote success ***"response": "waiting for server to promote.... done\nserver promoted\n"*** 2025-09-11T10:04:41Z INFO HA Take the leader success! 2025-09-11T10:06:54Z INFO HA This member is Cluster's leader 2025-09-11T10:06:54Z DEBUG HA Refresh leader ttl 2025-09-11T10:07:02Z INFO DCS-K8S pod selector: app.kubernetes.io/instance=vanilla-ekesge,app.kubernetes.io/managed-by=kubeblocks,apps.kubeblocks.io/component-name=postgresql 2025-09-11T10:07:02Z INFO DCS-K8S podlist: 3 2025-09-11T10:07:12Z INFO DCS-K8S pod selector: app.kubernetes.io/instance=vanilla-ekesge,app.kubernetes.io/managed-by=kubeblocks,apps.kubeblocks.io/component-name=postgresql 2025-09-11T10:07:12Z INFO DCS-K8S podlist: 3 2025-09-11T10:07:23Z INFO DCS-K8S pod selector: app.kubernetes.io/instance=vanilla-ekesge,app.kubernetes.io/managed-by=kubeblocks,apps.kubeblocks.io/component-name=postgresql 2025-09-11T10:07:23Z INFO DCS-K8S podlist: 3 2025-09-11T10:07:54Z INFO DCS-K8S pod selector: app.kubernetes.io/instance=vanilla-ekesge,app.kubernetes.io/managed-by=kubeblocks,apps.kubeblocks.io/component-name=postgresql 2025-09-11T10:07:54Z INFO DCS-K8S podlist: 2 2025-09-11T10:07:54Z INFO HA This member is Cluster's leader 2025-09-11T10:07:54Z DEBUG HA Refresh leader ttl 2025-09-11T10:08:54Z INFO HA This member is Cluster's leader 2025-09-11T10:08:54Z DEBUG HA Refresh leader ttl 2025-09-11T10:09:54Z INFO HA This member is Cluster's leader 2025-09-11T10:09:54Z DEBUG HA Refresh leader ttl 2025-09-11T10:10:54Z INFO HA This member is Cluster's leader 2025-09-11T10:10:54Z DEBUG HA Refresh leader ttl 2025-09-11T10:11:54Z INFO HA This member is Cluster's leader 2025-09-11T10:11:54Z DEBUG HA Refresh leader ttl 2025-09-11T10:12:54Z INFO HA This member is Cluster's leader 2025-09-11T10:12:54Z DEBUG HA Refresh leader ttl LB_TYPE is set to: intranet cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose vanilla-ekesge --auto-approve --force=true --type intranet --enable false --components postgresql --role-selector primary --namespace ns-qyyor ` OpsRequest vanilla-ekesge-expose-brjb2 created successfully, you can view the progress: kbcli cluster describe-ops vanilla-ekesge-expose-brjb2 -n ns-qyyor check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 check cluster status `kbcli cluster list vanilla-ekesge --show-labels --namespace ns-qyyor ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-ekesge ns-qyyor vanilla-postgresql WipeOut Running Sep 11,2025 17:20 UTC+0800 app.kubernetes.io/instance=vanilla-ekesge,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-ekesge --namespace ns-qyyor ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-ekesge-postgresql-0 ns-qyyor vanilla-ekesge postgresql Running primary 0 600m / 600m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-42771698-vmss000000/10.224.0.5 Sep 11,2025 18:01 UTC+0800 vanilla-ekesge-postgresql-1 ns-qyyor vanilla-ekesge postgresql Running secondary 0 600m / 600m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-42771698-vmss000004/10.224.0.6 Sep 11,2025 18:01 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-ekesge-postgresql-0;secondary: vanilla-ekesge-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-ekesge-postgresql-0 --namespace ns-qyyor -- psql -U postgres` check cluster connect done check ops status `kbcli cluster list-ops vanilla-ekesge --status all --namespace ns-qyyor ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Running 0/1 Sep 11,2025 18:13 UTC+0800 check ops status done ops_status:vanilla-ekesge-expose-brjb2 ns-qyyor Expose vanilla-ekesge postgresql Succeed 1/1 Sep 11,2025 18:13 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests.operations vanilla-ekesge-expose-brjb2 --namespace ns-qyyor ` opsrequest.operations.kubeblocks.io/vanilla-ekesge-expose-brjb2 patched `kbcli cluster delete-ops --name vanilla-ekesge-expose-brjb2 --force --auto-approve --namespace ns-qyyor ` OpsRequest vanilla-ekesge-expose-brjb2 deleted delete cluster vanilla-ekesge `kbcli cluster delete vanilla-ekesge --auto-approve --namespace ns-qyyor ` Cluster vanilla-ekesge deleted pod_info:vanilla-ekesge-postgresql-0 3/3 Running 18 (12m ago) 14m vanilla-ekesge-postgresql-1 3/3 Running 2 (11m ago) 14m No resources found in ns-qyyor namespace. delete cluster pod done No resources found in ns-qyyor namespace. check cluster resource non-exist OK: pvc No resources found in ns-qyyor namespace. delete cluster done No resources found in ns-qyyor namespace. No resources found in ns-qyyor namespace. No resources found in ns-qyyor namespace. Vanilla Postgresql Test Suite All Done! Test Engine: vanilla-postgresql Test Type: 20 --------------------------------------Vanilla Postgresql (Topology = Replicas 2) Test Result-------------------------------------- [PASSED]|[Create]|[ComponentDefinition=vanilla-postgresql-12-1.0.1;ComponentVersion=vanilla-postgresql;ServiceVersion=12.15.0;]|[Description=Create a cluster with the specified component definition vanilla-postgresql-12-1.0.1 and component version vanilla-postgresql and service version 12.15.0] [PASSED]|[Connect]|[ComponentName=postgresql]|[Description=Connect to the cluster] [PASSED]|[Expose]|[Enable=true;TYPE=intranet;ComponentName=postgresql]|[Description=Expose Enable the intranet service with postgresql component] [PASSED]|[No-Failover]|[HA=DNS Error;Durations=2m;ComponentName=postgresql]|[Description=Simulates conditions where pods experience DNS service errors for a period of time either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to DNS service errors.] [PASSED]|[No-Failover]|[HA=Network Partition;Durations=2m;ComponentName=postgresql]|[Description=Simulates network partition fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to partition network.] [PASSED]|[No-Failover]|[HA=DNS Random;Durations=2m;ComponentName=postgresql]|[Description=Simulates conditions where pods experience random IP addresses being returned by the DNS service for a period of time either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to the DNS service returning random IP addresses.] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [WARNING]|[VerticalScaling]|[ComponentName=postgresql]|[Description=VerticalScaling the cluster specify component postgresql] [PASSED]|[Failover]|[HA=Network Corrupt;Durations=2m;ComponentName=postgresql]|[Description=Simulates network corrupt fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to corrupt network.] [PASSED]|[No-Failover]|[HA=Full CPU;Durations=2m;ComponentName=postgresql]|[Description=Simulates conditions where pods experience CPU full either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to high CPU load.] [PASSED]|[No-Failover]|[HA=Network Duplicate;Durations=2m;ComponentName=postgresql]|[Description=Simulates network duplicate fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to duplicate network.] [PASSED]|[Bench]|[ComponentName=postgresql]|[Description=Bench the cluster service with postgresql component] [PASSED]|[Bench]|[HostType=LB;ComponentName=postgresql]|[Description=Bench the cluster LB service with postgresql component] [PASSED]|[No-Failover]|[HA=Time Offset;Durations=2m;ComponentName=postgresql]|[Description=Simulates a time offset scenario thereby testing the application's resilience to potential slowness/unavailability of some replicas due to time offset.] [PASSED]|[Failover]|[HA=Network Loss;Durations=2m;ComponentName=postgresql]|[Description=Simulates network loss fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to loss network.] [PASSED]|[Restart]|[-]|[Description=Restart the cluster] [PASSED]|[Failover]|[HA=Pod Failure;Durations=2m;ComponentName=postgresql]|[Description=Simulates conditions where pods experience failure for a period of time either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to failure.] [PASSED]|[Failover]|[HA=OOM;Durations=2m;ComponentName=postgresql]|[Description=Simulates conditions where pods experience OOM either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to high Memory load.] [PASSED]|[No-Failover]|[HA=Network Delay;Durations=2m;ComponentName=postgresql]|[Description=Simulates network delay fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to delay network.] [PASSED]|[HorizontalScaling Out]|[ComponentName=postgresql]|[Description=HorizontalScaling Out the cluster specify component postgresql] [PASSED]|[HorizontalScaling In]|[ComponentName=postgresql]|[Description=HorizontalScaling In the cluster specify component postgresql] [PASSED]|[VolumeExpansion]|[ComponentName=postgresql]|[Description=VolumeExpansion the cluster specify component postgresql] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Expose]|[Disable=true;TYPE=intranet;ComponentName=postgresql]|[Description=Expose Disable the intranet service with postgresql component] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]