source commons files source engines files source kubeblocks files kbcli is detected: /usr/local/bin/kbcli Kubernetes Env: v1.30.4-vke.4 check snapshot controller check snapshot controller done vke kb-default-sc found vke default-vsc found POD_RESOURCES: No resources found found default storage class: ebs-ssd KubeBlocks version is:1.0.0 skip upgrade KubeBlocks current KubeBlocks version: 1.0.0 check component definition No resources found KUBEBLOCKS NAMESPACE:kb-system get kubeblocks namespace done annotate vanilla-postgresql cmpd apps.kubeblocks.io/skip-immutable-check=true No resources found get helm repo list success found helm repo kbcli-test-addons `helm repo update kbcli-test-addons ` Hang tight while we grab the latest from your chart repositories... ...Successfully got an update from the "kbcli-test-addons" chart repository Update Complete. ⎈Happy Helming!⎈ KUBEBLOCKS NAMESPACE:kb-system get kubeblocks namespace done current KubeBlocks version: 1.0.0 `helm upgrade --install --namespace kb-system kb-addon-vanilla-postgresql kbcli-test-addons/vanilla-postgresql --version 1.0.0-alpha.0 --set image.registry=apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com --set images.registry=apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com ` Release "kb-addon-vanilla-postgresql" does not exist. Installing it now. NAME: kb-addon-vanilla-postgresql LAST DEPLOYED: Wed May 28 12:47:39 2025 NAMESPACE: kb-system STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: Release Information: Commit ID: "fdbf7a5c4f2c1ac3e699ef70e9791fae2b590198" Commit Time: "2025-05-26 17:41:18 +0800" Release Branch: "v1.0.0" Release Time: "2025-05-28 10:53:51 +0800" Enterprise: "false" set component version set component version:vanilla-postgresql set service versions:15.7.0,15.6.1-138,14.7.0,12.15.0 set service versions sorted:12.15.0,14.7.0,15.6.1-138,15.7.0 check component definition vanilla-postgresql status done set component name:postgresql found component version set vanilla-postgresql component definition set vanilla-postgresql component definition vanilla-postgresql-15-1.0.0-alpha.0 set replicas first:2,12.15.0|2,14.7.0|2,15.6.1-138|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 cluster topology: vanilla-postgresql set vanilla-postgresql component definition set vanilla-postgresql component definition vanilla-postgresql-15-1.0.0-alpha.0 LIMIT_CPU:0.5 LIMIT_MEMORY:0.5 storage size: 20 No resources found in default namespace. 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.0-alpha.0 by component version:vanilla-postgresql apiVersion: apps.kubeblocks.io/v1 kind: Cluster metadata: name: vanilla-sjjrzn namespace: default spec: clusterDef: vanilla-postgresql topology: vanilla-postgresql 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: 20Gi `kubectl apply -f test_create_vanilla-sjjrzn.yaml` cluster.apps.kubeblocks.io/vanilla-sjjrzn created apply test_create_vanilla-sjjrzn.yaml Success `rm -rf test_create_vanilla-sjjrzn.yaml` check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Creating May 28,2025 12:48 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 cluster_status:Creating cluster_status:Creating cluster_status:Creating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:48 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:50 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-0;secondary: vanilla-sjjrzn-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-0 --namespace default -- psql -U postgres` check cluster connect done `kubectl get secrets -l app.kubernetes.io/instance=vanilla-sjjrzn` `kubectl get secrets vanilla-sjjrzn-postgresql-account-postgres -o jsonpath="{.data.username}"` `kubectl get secrets vanilla-sjjrzn-postgresql-account-postgres -o jsonpath="{.data.password}"` `kubectl get secrets vanilla-sjjrzn-postgresql-account-postgres -o jsonpath="{.data.port}"` DB_USERNAME:postgres;DB_PASSWORD:5bZit9h789;DB_PORT:5432;DB_DATABASE: check pod vanilla-sjjrzn-postgresql-0 container_name postgresql exist password 5bZit9h789 check pod vanilla-sjjrzn-postgresql-0 container_name kbagent exist password 5bZit9h789 check pod vanilla-sjjrzn-postgresql-0 container_name config-manager exist password 5bZit9h789 No container logs contain secret password. describe cluster `kbcli cluster describe vanilla-sjjrzn --namespace default ` Name: vanilla-sjjrzn Created Time: May 28,2025 12:48 UTC+0800 NAMESPACE CLUSTER-DEFINITION TOPOLOGY STATUS TERMINATION-POLICY default vanilla-postgresql vanilla-postgresql Running WipeOut Endpoints: COMPONENT INTERNAL EXTERNAL postgresql vanilla-sjjrzn-postgresql.default.svc.cluster.local:5432 Topology: COMPONENT SERVICE-VERSION INSTANCE ROLE STATUS AZ NODE CREATED-TIME postgresql 12.15.0 vanilla-sjjrzn-postgresql-0 primary Running cn-guangzhou-b 192.168.0.42/192.168.0.42 May 28,2025 12:48 UTC+0800 postgresql 12.15.0 vanilla-sjjrzn-postgresql-1 secondary Running cn-guangzhou-b 192.168.0.42/192.168.0.42 May 28,2025 12:50 UTC+0800 Resources Allocation: COMPONENT INSTANCE-TEMPLATE CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS postgresql 500m / 500m 512Mi / 512Mi data:20Gi ebs-ssd Images: COMPONENT COMPONENT-DEFINITION IMAGE postgresql vanilla-postgresql-12-1.0.0-alpha.0 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/postgres:12.15 apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/kubeblocks-tools:1.0.0 Data Protection: BACKUP-REPO AUTO-BACKUP BACKUP-SCHEDULE BACKUP-METHOD BACKUP-RETENTION RECOVERABLE-TIME Show cluster events: kbcli cluster list-events -n default vanilla-sjjrzn `kbcli cluster label vanilla-sjjrzn app.kubernetes.io/instance- --namespace default ` label "app.kubernetes.io/instance" not found. `kbcli cluster label vanilla-sjjrzn app.kubernetes.io/instance=vanilla-sjjrzn --namespace default ` `kbcli cluster label vanilla-sjjrzn --list --namespace default ` NAME NAMESPACE LABELS vanilla-sjjrzn default app.kubernetes.io/instance=vanilla-sjjrzn clusterdefinition.kubeblocks.io/name=vanilla-postgresql label cluster app.kubernetes.io/instance=vanilla-sjjrzn Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=vanilla-sjjrzn --namespace default ` `kbcli cluster label vanilla-sjjrzn --list --namespace default ` NAME NAMESPACE LABELS vanilla-sjjrzn default app.kubernetes.io/instance=vanilla-sjjrzn case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=vanilla-postgresql label cluster case.name=kbcli.test1 Success `kbcli cluster label vanilla-sjjrzn case.name=kbcli.test2 --overwrite --namespace default ` `kbcli cluster label vanilla-sjjrzn --list --namespace default ` NAME NAMESPACE LABELS vanilla-sjjrzn default app.kubernetes.io/instance=vanilla-sjjrzn case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=vanilla-postgresql label cluster case.name=kbcli.test2 Success `kbcli cluster label vanilla-sjjrzn case.name- --namespace default ` `kbcli cluster label vanilla-sjjrzn --list --namespace default ` NAME NAMESPACE LABELS vanilla-sjjrzn default app.kubernetes.io/instance=vanilla-sjjrzn clusterdefinition.kubeblocks.io/name=vanilla-postgresql delete cluster label case.name Success cluster connect `echo 'select 1' | kubectl exec -it vanilla-sjjrzn-postgresql-0 --namespace default -- 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-sjjrzn --auto-approve --force=true --type intranet --enable true --components postgresql --role-selector primary --namespace default ` OpsRequest vanilla-sjjrzn-expose-dgvzj created successfully, you can view the progress: kbcli cluster describe-ops vanilla-sjjrzn-expose-dgvzj -n default check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-expose-dgvzj default Expose vanilla-sjjrzn postgresql Running 0/1 May 28,2025 12:51 UTC+0800 check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Running May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:48 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:20Gi 192.168.0.42/192.168.0.42 May 28,2025 12:50 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-0;secondary: vanilla-sjjrzn-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-0 --namespace default -- psql -U postgres` check cluster connect done check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-expose-dgvzj default Expose vanilla-sjjrzn postgresql Running 0/1 May 28,2025 12:51 UTC+0800 ops_status:vanilla-sjjrzn-expose-dgvzj default Expose vanilla-sjjrzn postgresql Running 0/1 May 28,2025 12:51 UTC+0800 check ops status done ops_status:vanilla-sjjrzn-expose-dgvzj default Expose vanilla-sjjrzn postgresql Succeed 1/1 May 28,2025 12:51 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations vanilla-sjjrzn-expose-dgvzj --namespace default ` opsrequest.operations.kubeblocks.io/vanilla-sjjrzn-expose-dgvzj patched `kbcli cluster delete-ops --name vanilla-sjjrzn-expose-dgvzj --force --auto-approve --namespace default ` OpsRequest vanilla-sjjrzn-expose-dgvzj deleted skip Reconfiguring: `kubectl get pvc -l app.kubernetes.io/instance=vanilla-sjjrzn,apps.kubeblocks.io/component-name=postgresql,apps.kubeblocks.io/vct-name=data --namespace default ` cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in vanilla-sjjrzn namespace. `kbcli cluster volume-expand vanilla-sjjrzn --auto-approve --force=true --components postgresql --volume-claim-templates data --storage 21Gi --namespace default ` OpsRequest vanilla-sjjrzn-volumeexpansion-hrtwn created successfully, you can view the progress: kbcli cluster describe-ops vanilla-sjjrzn-volumeexpansion-hrtwn -n default check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-volumeexpansion-hrtwn default VolumeExpansion vanilla-sjjrzn postgresql Running 0/2 May 28,2025 12:52 UTC+0800 check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Updating May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,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 check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:48 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:50 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-0;secondary: vanilla-sjjrzn-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-0 --namespace default -- psql -U postgres` check cluster connect done No resources found in vanilla-sjjrzn namespace. check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-volumeexpansion-hrtwn default VolumeExpansion vanilla-sjjrzn postgresql Succeed 2/2 May 28,2025 12:52 UTC+0800 check ops status done ops_status:vanilla-sjjrzn-volumeexpansion-hrtwn default VolumeExpansion vanilla-sjjrzn postgresql Succeed 2/2 May 28,2025 12:52 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations vanilla-sjjrzn-volumeexpansion-hrtwn --namespace default ` opsrequest.operations.kubeblocks.io/vanilla-sjjrzn-volumeexpansion-hrtwn patched `kbcli cluster delete-ops --name vanilla-sjjrzn-volumeexpansion-hrtwn --force --auto-approve --namespace default ` OpsRequest vanilla-sjjrzn-volumeexpansion-hrtwn deleted 11 cluster postgresql scale-out check cluster status before ops check cluster status done cluster_status:Running No resources found in vanilla-sjjrzn namespace. `kbcli cluster scale-out vanilla-sjjrzn --auto-approve --force=true --components postgresql --replicas 1 --namespace default ` OpsRequest vanilla-sjjrzn-horizontalscaling-8wkh7 created successfully, you can view the progress: kbcli cluster describe-ops vanilla-sjjrzn-horizontalscaling-8wkh7 -n default check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-horizontalscaling-8wkh7 default HorizontalScaling vanilla-sjjrzn postgresql Running 0/1 May 28,2025 12:53 UTC+0800 check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Updating May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,clusterdefinition.kubeblocks.io/name=vanilla-postgresql cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:48 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:50 UTC+0800 vanilla-sjjrzn-postgresql-2 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:53 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-0;secondary: vanilla-sjjrzn-postgresql-1 vanilla-sjjrzn-postgresql-2 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-0 --namespace default -- psql -U postgres` check cluster connect done No resources found in vanilla-sjjrzn namespace. check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-horizontalscaling-8wkh7 default HorizontalScaling vanilla-sjjrzn postgresql Succeed 1/1 May 28,2025 12:53 UTC+0800 check ops status done ops_status:vanilla-sjjrzn-horizontalscaling-8wkh7 default HorizontalScaling vanilla-sjjrzn postgresql Succeed 1/1 May 28,2025 12:53 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations vanilla-sjjrzn-horizontalscaling-8wkh7 --namespace default ` opsrequest.operations.kubeblocks.io/vanilla-sjjrzn-horizontalscaling-8wkh7 patched `kbcli cluster delete-ops --name vanilla-sjjrzn-horizontalscaling-8wkh7 --force --auto-approve --namespace default ` OpsRequest vanilla-sjjrzn-horizontalscaling-8wkh7 deleted cluster postgresql scale-in check cluster status before ops check cluster status done cluster_status:Running No resources found in vanilla-sjjrzn namespace. `kbcli cluster scale-in vanilla-sjjrzn --auto-approve --force=true --components postgresql --replicas 1 --namespace default ` OpsRequest vanilla-sjjrzn-horizontalscaling-nh782 created successfully, you can view the progress: kbcli cluster describe-ops vanilla-sjjrzn-horizontalscaling-nh782 -n default check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-horizontalscaling-nh782 default HorizontalScaling vanilla-sjjrzn postgresql Running 0/1 May 28,2025 12:54 UTC+0800 check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Running May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:48 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:50 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-0;secondary: vanilla-sjjrzn-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-0 --namespace default -- psql -U postgres` check cluster connect done No resources found in vanilla-sjjrzn namespace. check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-horizontalscaling-nh782 default HorizontalScaling vanilla-sjjrzn postgresql Succeed 1/1 May 28,2025 12:54 UTC+0800 check ops status done ops_status:vanilla-sjjrzn-horizontalscaling-nh782 default HorizontalScaling vanilla-sjjrzn postgresql Succeed 1/1 May 28,2025 12:54 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations vanilla-sjjrzn-horizontalscaling-nh782 --namespace default ` opsrequest.operations.kubeblocks.io/vanilla-sjjrzn-horizontalscaling-nh782 patched `kbcli cluster delete-ops --name vanilla-sjjrzn-horizontalscaling-nh782 --force --auto-approve --namespace default ` OpsRequest vanilla-sjjrzn-horizontalscaling-nh782 deleted cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart vanilla-sjjrzn --auto-approve --force=true --namespace default ` OpsRequest vanilla-sjjrzn-restart-lnfkw created successfully, you can view the progress: kbcli cluster describe-ops vanilla-sjjrzn-restart-lnfkw -n default check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-restart-lnfkw default Restart vanilla-sjjrzn postgresql Running 0/2 May 28,2025 12:54 UTC+0800 check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Updating May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,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-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:54 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:54 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-1;secondary: vanilla-sjjrzn-postgresql-0 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-1 --namespace default -- psql -U postgres` check cluster connect done check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-restart-lnfkw default Restart vanilla-sjjrzn postgresql Succeed 2/2 May 28,2025 12:54 UTC+0800 check ops status done ops_status:vanilla-sjjrzn-restart-lnfkw default Restart vanilla-sjjrzn postgresql Succeed 2/2 May 28,2025 12:54 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations vanilla-sjjrzn-restart-lnfkw --namespace default ` opsrequest.operations.kubeblocks.io/vanilla-sjjrzn-restart-lnfkw patched `kbcli cluster delete-ops --name vanilla-sjjrzn-restart-lnfkw --force --auto-approve --namespace default ` OpsRequest vanilla-sjjrzn-restart-lnfkw deleted cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop vanilla-sjjrzn --auto-approve --force=true --namespace default ` OpsRequest vanilla-sjjrzn-stop-z464x created successfully, you can view the progress: kbcli cluster describe-ops vanilla-sjjrzn-stop-z464x -n default check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-stop-z464x default Stop vanilla-sjjrzn postgresql Running 0/2 May 28,2025 12:55 UTC+0800 check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Stopped May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Stopped check pod status `kbcli cluster list-instances vanilla-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME check pod status done check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-stop-z464x default Stop vanilla-sjjrzn postgresql Succeed 2/2 May 28,2025 12:55 UTC+0800 check ops status done ops_status:vanilla-sjjrzn-stop-z464x default Stop vanilla-sjjrzn postgresql Succeed 2/2 May 28,2025 12:55 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations vanilla-sjjrzn-stop-z464x --namespace default ` opsrequest.operations.kubeblocks.io/vanilla-sjjrzn-stop-z464x patched `kbcli cluster delete-ops --name vanilla-sjjrzn-stop-z464x --force --auto-approve --namespace default ` OpsRequest vanilla-sjjrzn-stop-z464x deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start vanilla-sjjrzn --force=true --namespace default ` OpsRequest vanilla-sjjrzn-start-s22qg created successfully, you can view the progress: kbcli cluster describe-ops vanilla-sjjrzn-start-s22qg -n default check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-start-s22qg default Start vanilla-sjjrzn postgresql Running 0/2 May 28,2025 12:55 UTC+0800 check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Updating May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,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-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:55 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:55 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-0;secondary: vanilla-sjjrzn-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-0 --namespace default -- psql -U postgres` check cluster connect done check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-start-s22qg default Start vanilla-sjjrzn postgresql Succeed 2/2 May 28,2025 12:55 UTC+0800 check ops status done ops_status:vanilla-sjjrzn-start-s22qg default Start vanilla-sjjrzn postgresql Succeed 2/2 May 28,2025 12:55 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations vanilla-sjjrzn-start-s22qg --namespace default ` opsrequest.operations.kubeblocks.io/vanilla-sjjrzn-start-s22qg patched `kbcli cluster delete-ops --name vanilla-sjjrzn-start-s22qg --force --auto-approve --namespace default ` OpsRequest vanilla-sjjrzn-start-s22qg deleted test failover kill1 check node drain check node drain success `kill 1` 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 exec return message: check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Running May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:55 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:55 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-1;secondary: vanilla-sjjrzn-postgresql-0 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-1 --namespace default -- psql -U postgres` check cluster connect done check failover pod name failover pod name:vanilla-sjjrzn-postgresql-1 failover kill1 Success test failover delete pod:vanilla-sjjrzn-postgresql-1 `kubectl delete pod vanilla-sjjrzn-postgresql-1 --namespace default ` pod "vanilla-sjjrzn-postgresql-1" deleted check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Updating May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,clusterdefinition.kubeblocks.io/name=vanilla-postgresql cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:55 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 500m / 500m 512Mi / 512Mi data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:56 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-0;secondary: vanilla-sjjrzn-postgresql-1 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-0 --namespace default -- psql -U postgres` check cluster connect done check failover pod name failover pod name:vanilla-sjjrzn-postgresql-0 failover Success check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale vanilla-sjjrzn --auto-approve --force=true --components postgresql --cpu 600m --memory 0.6Gi --namespace default ` OpsRequest vanilla-sjjrzn-verticalscaling-vbw5g created successfully, you can view the progress: kbcli cluster describe-ops vanilla-sjjrzn-verticalscaling-vbw5g -n default check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-verticalscaling-vbw5g default VerticalScaling vanilla-sjjrzn postgresql Running 0/2 May 28,2025 12:56 UTC+0800 check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Updating May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,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-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 600m / 600m 644245094400m / 644245094400m data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:56 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 600m / 600m 644245094400m / 644245094400m data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:56 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-1;secondary: vanilla-sjjrzn-postgresql-0 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-1 --namespace default -- psql -U postgres` check cluster connect done check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-verticalscaling-vbw5g default VerticalScaling vanilla-sjjrzn postgresql Succeed 2/2 May 28,2025 12:56 UTC+0800 check ops status done ops_status:vanilla-sjjrzn-verticalscaling-vbw5g default VerticalScaling vanilla-sjjrzn postgresql Succeed 2/2 May 28,2025 12:56 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations vanilla-sjjrzn-verticalscaling-vbw5g --namespace default ` opsrequest.operations.kubeblocks.io/vanilla-sjjrzn-verticalscaling-vbw5g patched `kbcli cluster delete-ops --name vanilla-sjjrzn-verticalscaling-vbw5g --force --auto-approve --namespace default ` OpsRequest vanilla-sjjrzn-verticalscaling-vbw5g deleted `kubectl get secrets -l app.kubernetes.io/instance=vanilla-sjjrzn` `kubectl get secrets vanilla-sjjrzn-postgresql-account-postgres -o jsonpath="{.data.username}"` `kubectl get secrets vanilla-sjjrzn-postgresql-account-postgres -o jsonpath="{.data.password}"` `kubectl get secrets vanilla-sjjrzn-postgresql-account-postgres -o jsonpath="{.data.port}"` DB_USERNAME:postgres;DB_PASSWORD:5bZit9h789;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-sjjrzn namespace: default spec: containers: - name: test-sysbench imagePullPolicy: IfNotPresent image: apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/customsuites:latest env: - name: TYPE value: "2" - name: FLAG value: "0" - name: CONFIGS value: "mode:all,driver:pgsql,host:vanilla-sjjrzn-postgresql.default.svc.cluster.local,user:postgres,password:5bZit9h789,port:5432,db:benchtest,tables:5,threads:4,times:10,size:1000,type:oltp_read_write" restartPolicy: Never `kubectl apply -f benchtest-vanilla-sjjrzn.yaml` pod/benchtest-vanilla-sjjrzn created apply benchtest-vanilla-sjjrzn.yaml Success `rm -rf benchtest-vanilla-sjjrzn.yaml` check pod status pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 0s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 5s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 10s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 15s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 20s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 25s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 31s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 36s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 41s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 46s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 52s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 57s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 1/1 Running 0 62s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 1/1 Running 0 67s check pod benchtest-vanilla-sjjrzn status done pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 Completed 0 72s `kubectl logs benchtest-vanilla-sjjrzn --tail 30 --namespace default ` [ 7s ] thds: 4 tps: 773.00 qps: 15492.02 (r/w/o: 10851.02/3088.00/1553.00) lat (ms,99%): 82.96 err/s: 1.00 reconn/s: 0.00 [ 8s ] thds: 4 tps: 60.00 qps: 1200.98 (r/w/o: 843.99/235.00/122.00) lat (ms,99%): 995.51 err/s: 1.00 reconn/s: 0.00 [ 9s ] thds: 4 tps: 9.00 qps: 195.00 (r/w/o: 136.00/41.00/18.00) lat (ms,99%): 1.04 err/s: 0.00 reconn/s: 0.00 [ 10s ] thds: 4 tps: 878.02 qps: 17667.50 (r/w/o: 12376.35/3513.10/1778.05) lat (ms,99%): 82.96 err/s: 7.00 reconn/s: 0.00 SQL statistics: queries performed: read: 70910 write: 20177 other: 10162 total: 101249 transactions: 5043 (500.46 per sec.) queries: 101249 (10047.72 per sec.) ignored errors: 22 (2.18 per sec.) reconnects: 0 (0.00 per sec.) General statistics: total time: 10.0764s total number of events: 5043 Latency (ms): min: 0.59 avg: 7.99 max: 1084.35 99th percentile: 82.96 sum: 40295.04 Threads fairness: events (avg/stddev): 1260.7500/14.31 execution time (avg/stddev): 10.0738/0.00 `kubectl delete pod benchtest-vanilla-sjjrzn --force --namespace default ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. pod "benchtest-vanilla-sjjrzn" force deleted LB_TYPE is set to: intranet No resources found in default namespace. `kubectl get secrets -l app.kubernetes.io/instance=vanilla-sjjrzn` `kubectl get secrets vanilla-sjjrzn-postgresql-account-postgres -o jsonpath="{.data.username}"` `kubectl get secrets vanilla-sjjrzn-postgresql-account-postgres -o jsonpath="{.data.password}"` `kubectl get secrets vanilla-sjjrzn-postgresql-account-postgres -o jsonpath="{.data.port}"` DB_USERNAME:postgres;DB_PASSWORD:5bZit9h789;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-sjjrzn namespace: default spec: containers: - name: test-sysbench imagePullPolicy: IfNotPresent image: apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/customsuites:latest env: - name: TYPE value: "2" - name: FLAG value: "0" - name: CONFIGS value: "mode:all,driver:pgsql,host:118.145.200.221,user:postgres,password:5bZit9h789,port:5432,db:benchtest,tables:5,threads:4,times:10,size:1000,type:oltp_read_write" restartPolicy: Never `kubectl apply -f benchtest-vanilla-sjjrzn.yaml` pod/benchtest-vanilla-sjjrzn created apply benchtest-vanilla-sjjrzn.yaml Success `rm -rf benchtest-vanilla-sjjrzn.yaml` check pod status pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 ContainerCreating 0 1s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 1/1 Running 0 5s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 1/1 Running 0 10s pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 1/1 Running 0 15s check pod benchtest-vanilla-sjjrzn status done pod_status:NAME READY STATUS RESTARTS AGE benchtest-vanilla-sjjrzn 0/1 Completed 0 21s `kubectl logs benchtest-vanilla-sjjrzn --tail 30 --namespace default ` [ 7s ] thds: 4 tps: 668.99 qps: 13410.90 (r/w/o: 9392.93/2671.98/1345.99) lat (ms,99%): 81.48 err/s: 1.00 reconn/s: 0.00 [ 8s ] thds: 4 tps: 676.97 qps: 13581.48 (r/w/o: 9503.64/2716.90/1360.95) lat (ms,99%): 81.48 err/s: 2.00 reconn/s: 0.00 [ 9s ] thds: 4 tps: 680.03 qps: 13635.62 (r/w/o: 9548.43/2717.12/1370.06) lat (ms,99%): 82.96 err/s: 2.00 reconn/s: 0.00 [ 10s ] thds: 4 tps: 677.00 qps: 13594.01 (r/w/o: 9520.01/2707.00/1367.00) lat (ms,99%): 81.48 err/s: 4.00 reconn/s: 0.00 SQL statistics: queries performed: read: 95914 write: 27291 other: 13757 total: 136962 transactions: 6822 (676.99 per sec.) queries: 136962 (13591.64 per sec.) ignored errors: 29 (2.88 per sec.) reconnects: 0 (0.00 per sec.) General statistics: total time: 10.0765s total number of events: 6822 Latency (ms): min: 0.61 avg: 5.91 max: 89.46 99th percentile: 81.48 sum: 40290.78 Threads fairness: events (avg/stddev): 1705.5000/8.53 execution time (avg/stddev): 10.0727/0.00 `kubectl delete pod benchtest-vanilla-sjjrzn --force --namespace default ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. pod "benchtest-vanilla-sjjrzn" force deleted skip Reconfiguring: cluster update terminationPolicy WipeOut `kbcli cluster update vanilla-sjjrzn --termination-policy=WipeOut --namespace default ` cluster.apps.kubeblocks.io/vanilla-sjjrzn updated (no change) check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Running May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 600m / 600m 644245094400m / 644245094400m data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:56 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 600m / 600m 644245094400m / 644245094400m data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:56 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-1;secondary: vanilla-sjjrzn-postgresql-0 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-1 --namespace default -- psql -U postgres` check cluster connect done cluster list-logs `kbcli cluster list-logs vanilla-sjjrzn --namespace default ` No log files found. cluster logs `kbcli cluster logs vanilla-sjjrzn --tail 30 --namespace default ` Defaulted container "postgresql" out of: postgresql, kbagent, config-manager, init-syncer (init), kbagent-worker (init), install-config-manager-tool (init) 2025-05-28T04:56:40Z INFO HA wait for db service to be ready 2025-05-28T04:56:40Z INFO HA DB Service is running 2025-05-28T04:56:40Z INFO PostgreSQL DB startup ready 2025-05-28T04:56:41Z INFO PostgreSQL no action coz i still follow the leader:vanilla-sjjrzn-postgresql-0 2025-05-28T04:56:42Z INFO DCS-K8S Found switchover Setting {"configmap": {"candidate":"","leader":"vanilla-sjjrzn-postgresql-0"}} 2025-05-28T04:56:43Z INFO DCS-K8S Found switchover Setting {"configmap": {"candidate":"","leader":"vanilla-sjjrzn-postgresql-0"}} 2025-05-28T04:56:43Z INFO HA Cluster has no leader, attempt to take the leader 2025-05-28T04:56:43Z ERROR PostgreSQL get timeline with host:vanilla-sjjrzn-postgresql-0.vanilla-sjjrzn-postgresql-headless.default.svc failed {"error": "exec command psql -h vanilla-sjjrzn-postgresql-0.vanilla-sjjrzn-postgresql-headless.default.svc replication=true -c IDENTIFY_SYSTEM failed, err:exit status 2, stderr:psql: error: connection to server at \"vanilla-sjjrzn-postgresql-0.vanilla-sjjrzn-postgresql-headless.default.svc\" (192.168.0.53), port 5432 failed: No route to host\n\tIs the server running on that host and accepting TCP/IP connections?\n", "errorVerbose": "exec command psql -h vanilla-sjjrzn-postgresql-0.vanilla-sjjrzn-postgresql-headless.default.svc replication=true -c IDENTIFY_SYSTEM failed, err:exit status 2, stderr:psql: error: connection to server at \"vanilla-sjjrzn-postgresql-0.vanilla-sjjrzn-postgresql-headless.default.svc\" (192.168.0.53), port 5432 failed: No route to host\n\tIs the server running on that host and accepting TCP/IP connections?\n\ngithub.com/apecloud/syncer/engines/postgres.ExecCommand\n\t/src/engines/postgres/local_command.go:65\ngithub.com/apecloud/syncer/engines/postgres.Psql\n\t/src/engines/postgres/local_command.go:80\ngithub.com/apecloud/syncer/engines/postgres/vanillapostgresql.(*Manager).getReplicationTimeLine\n\t/src/engines/postgres/vanillapostgresql/status.go:200\ngithub.com/apecloud/syncer/engines/postgres/vanillapostgresql.(*Manager).IsMemberLagging\n\t/src/engines/postgres/vanillapostgresql/manager.go:226\ngithub.com/apecloud/syncer/highavailability.(*Ha).isMinimumLag\n\t/src/highavailability/ha.go:356\ngithub.com/apecloud/syncer/highavailability.(*Ha).IsHealthiestMember\n\t/src/highavailability/ha.go:309\ngithub.com/apecloud/syncer/highavailability.(*Ha).RunCycle\n\t/src/highavailability/ha.go:157\ngithub.com/apecloud/syncer/highavailability.(*Ha).Start\n\t/src/highavailability/ha.go:278\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1695"} github.com/apecloud/syncer/engines/postgres/vanillapostgresql.(*Manager).IsMemberLagging /src/engines/postgres/vanillapostgresql/manager.go:228 github.com/apecloud/syncer/highavailability.(*Ha).isMinimumLag /src/highavailability/ha.go:356 github.com/apecloud/syncer/highavailability.(*Ha).IsHealthiestMember /src/highavailability/ha.go:309 github.com/apecloud/syncer/highavailability.(*Ha).RunCycle /src/highavailability/ha.go:157 github.com/apecloud/syncer/highavailability.(*Ha).Start /src/highavailability/ha.go:278 2025-05-28T04:56:43Z INFO PostgreSQL promote success {"response": "waiting for server to promote.... done\nserver promoted\n"} 2025-05-28T04:56:43Z INFO HA Take the leader success! 2025-05-28T04:56:43Z INFO HA End switchover record failed {"error": "no matched ha record"} 2025-05-28T04:56:43Z INFO HA Refresh leader ttl 2025-05-28T04:57:41Z INFO HA This member is Cluster's leader 2025-05-28T04:57:41Z DEBUG HA Refresh leader ttl 2025-05-28T04:58:41Z INFO HA This member is Cluster's leader 2025-05-28T04:58:41Z DEBUG HA Refresh leader ttl 2025-05-28T04:59:41Z INFO HA This member is Cluster's leader 2025-05-28T04:59:41Z DEBUG HA Refresh leader ttl 2025-05-28T05:00:41Z INFO HA This member is Cluster's leader 2025-05-28T05:00:41Z DEBUG HA Refresh leader ttl cluster logs specify instance and container `kbcli cluster logs vanilla-sjjrzn --tail 30 --instance vanilla-sjjrzn-postgresql-1 -c kbagent --namespace default ` 2025-05-28T04:56:35Z INFO create service Action {"actions": "switchover,roleProbe"} 2025-05-28T04:56:35Z INFO create service Probe {"probes": "roleProbe"} 2025-05-28T04:56:35Z INFO create service Streaming {"actions": ""} 2025-05-28T04:56:35Z INFO service Action started... 2025-05-28T04:56:35Z INFO service Probe started... 2025-05-28T04:56:35Z INFO service Streaming started... 2025-05-28T04:56:35Z INFO starting the HTTP server 2025-05-28T04:56:35Z INFO register service to server {"service": "Action", "method": "POST", "uri": "/v1.0/action"} 2025-05-28T04:56:35Z INFO register service to server {"service": "Probe", "method": "POST", "uri": "/v1.0/probe"} 2025-05-28T04:56:35Z INFO register service to server {"service": "Streaming", "method": "POST", "uri": "/v1.0/streaming"} 2025-05-28T04:56:35Z INFO starting the streaming server 2025-05-28T04:56:35Z INFO probe started {"probe": "roleProbe", "config": {"instance":"vanilla-sjjrzn-postgresql","action":"roleProbe","periodSeconds":1}} 2025-05-28T04:56:36Z INFO send probe event {"probe": "roleProbe", "probe": "roleProbe", "code": 0, "output": "secondary", "message": ""} 2025-05-28T04:56:43Z INFO send probe event {"probe": "roleProbe", "probe": "roleProbe", "code": 0, "output": "primary", "message": ""} LB_TYPE is set to: intranet cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose vanilla-sjjrzn --auto-approve --force=true --type intranet --enable false --components postgresql --role-selector primary --namespace default ` OpsRequest vanilla-sjjrzn-expose-tcw9h created successfully, you can view the progress: kbcli cluster describe-ops vanilla-sjjrzn-expose-tcw9h -n default check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-expose-tcw9h default Expose vanilla-sjjrzn postgresql Running 0/1 May 28,2025 13:00 UTC+0800 check cluster status `kbcli cluster list vanilla-sjjrzn --show-labels --namespace default ` NAME NAMESPACE CLUSTER-DEFINITION TERMINATION-POLICY STATUS CREATED-TIME LABELS vanilla-sjjrzn default vanilla-postgresql WipeOut Running May 28,2025 12:48 UTC+0800 app.kubernetes.io/instance=vanilla-sjjrzn,clusterdefinition.kubeblocks.io/name=vanilla-postgresql check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances vanilla-sjjrzn --namespace default ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME vanilla-sjjrzn-postgresql-0 default vanilla-sjjrzn postgresql Running secondary cn-guangzhou-b 600m / 600m 644245094400m / 644245094400m data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:56 UTC+0800 vanilla-sjjrzn-postgresql-1 default vanilla-sjjrzn postgresql Running primary cn-guangzhou-b 600m / 600m 644245094400m / 644245094400m data:21Gi 192.168.0.42/192.168.0.42 May 28,2025 12:56 UTC+0800 check pod status done check cluster role check cluster role done primary: vanilla-sjjrzn-postgresql-1;secondary: vanilla-sjjrzn-postgresql-0 check cluster connect `echo '' | kubectl exec -it vanilla-sjjrzn-postgresql-1 --namespace default -- psql -U postgres` check cluster connect done check ops status `kbcli cluster list-ops vanilla-sjjrzn --status all --namespace default ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME vanilla-sjjrzn-expose-tcw9h default Expose vanilla-sjjrzn postgresql Succeed 1/1 May 28,2025 13:00 UTC+0800 check ops status done ops_status:vanilla-sjjrzn-expose-tcw9h default Expose vanilla-sjjrzn postgresql Succeed 1/1 May 28,2025 13:00 UTC+0800 `kubectl patch -p '{"metadata":{"finalizers":[]}}' --type=merge opsrequests.operations vanilla-sjjrzn-expose-tcw9h --namespace default ` opsrequest.operations.kubeblocks.io/vanilla-sjjrzn-expose-tcw9h patched `kbcli cluster delete-ops --name vanilla-sjjrzn-expose-tcw9h --force --auto-approve --namespace default ` OpsRequest vanilla-sjjrzn-expose-tcw9h deleted delete cluster vanilla-sjjrzn `kbcli cluster delete vanilla-sjjrzn --auto-approve --namespace default ` Cluster vanilla-sjjrzn deleted pod_info:vanilla-sjjrzn-postgresql-0 3/3 Running 0 4m26s vanilla-sjjrzn-postgresql-1 3/3 Running 0 4m39s No resources found in default namespace. delete cluster pod done No resources found in default namespace. check cluster resource non-exist OK: pvc No resources found in default namespace. delete cluster done No resources found in default namespace. No resources found in default namespace. No resources found in default namespace. Vanilla Postgresql Test Suite All Done! --------------------------------------Vanilla Postgresql (Topology = vanilla-postgresql Replicas 2) Test Result-------------------------------------- [PASSED]|[Create]|[ComponentDefinition=vanilla-postgresql-12-1.0.0-alpha.0;ComponentVersion=vanilla-postgresql;ServiceVersion=12.15.0;]|[Description=Create a cluster with the specified component definition vanilla-postgresql-12-1.0.0-alpha.0 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]|[VolumeExpansion]|[ComponentName=postgresql]|[Description=VolumeExpansion the cluster specify component postgresql] [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]|[Restart]|[-]|[Description=Restart the cluster] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [PASSED]|[Failover]|[HA=Kill 1;ComponentName=postgresql]|[Description=Simulates conditions where process 1 killed either due to expected/undesired processes thereby testing the application's resilience to unavailability of some replicas due to abnormal termination signals.] [PASSED]|[Failover]|[HA=Delete Pod;ComponentName=postgresql]|[Description=Simulates conditions where pods terminating forced/graceful thereby testing deployment sanity (replica availability & uninterrupted service) and recovery workflow of the application.] [PASSED]|[VerticalScaling]|[ComponentName=postgresql]|[Description=VerticalScaling the cluster specify component postgresql] [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]|[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]