Skip to content Navigation Menu apecloud kubeblocks Type / to search Code Issues 144 Pull requests 11 Discussions Actions Projects 1 Security 3 Insights Settings E2E Test KBCLI kbcli: to v0.9.5 aks:1.32:amd64 apecloud-mysql|postgresql|redis|mongodb|kafka|asmysql|elasticsearch|oceanbase-ent|rabbitmq|gaussdb|damengdb|kingbase #2186 Jobs Run details Annotations 1 error aks / test-postgresql / test postgresql failed 2 hours ago in 2h 54m 35s Search logs 5s 1s 0s 0s 1s 1s 0s 0s 0s 0s 0s 0s 22s 0s 1s 0s 0s 0s 2h 54m 0s Run if [[ -d kubeblocks-addons/examples ]]; then k8s-cluster-name:cicd-aks-6ei3v2ud bash .github/utils/kbcli-test.sh --type '2' --kubeblocks-version '0.9.5' --region 'eastus' --cloud-provider 'aks' --cluster-name 'cicd-aks-6ei3v2ud' --args ' --generate-output true --chaos-mesh true --drain-node true ' previous_version: kubeblocks_version:0.9.5 bash test/kbcli/test_kbcli_0.9.sh --type 2 --version 0.9.5 --generate-output true --chaos-mesh true --drain-node true --random-namespace true --region eastus --cloud-provider aks CURRENT_TEST_DIR:test/kbcli source commons files source engines files source kubeblocks files `kubectl get namespace | grep ns-yztjr ` `kubectl create namespace ns-yztjr` namespace/ns-yztjr created create namespace ns-yztjr done download kbcli `gh release list --repo apecloud/kbcli --limit 100 | (grep "0.9" || true)` `curl -fsSL https://kubeblocks.io/installer/install_cli.sh | bash -s v0.9.5-beta.8` Your system is linux_amd64 Installing kbcli ... Downloading ... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 54 32.1M 54 17.5M 0 0 75.5M 0 --:--:-- --:--:-- --:--:-- 75.5M 100 32.1M 100 32.1M 0 0 119M 0 --:--:-- --:--:-- --:--:-- 406M kbcli installed successfully. Kubernetes: v1.32.6 KubeBlocks: 0.9.5 kbcli: 0.9.5-beta.8 WARNING: version difference between kbcli (0.9.5-beta.8) and kubeblocks (0.9.5) Make sure your docker service is running and begin your journey with kbcli: kbcli playground init For more information on how to get started, please visit: https://kubeblocks.io download kbcli v0.9.5-beta.8 done Kubernetes: v1.32.6 KubeBlocks: 0.9.5 kbcli: 0.9.5-beta.8 WARNING: version difference between kbcli (0.9.5-beta.8) and kubeblocks (0.9.5) Kubernetes Env: v1.32.6 POD_RESOURCES: aks kb-default-sc found aks default-vsc found found default storage class: default kubeblocks version is:0.9.5 skip upgrade kubeblocks Error: no repositories to show helm repo add chaos-mesh https://charts.chaos-mesh.org "chaos-mesh" has been added to your repositories add helm chart repo chaos-mesh success chaos mesh already installed check cluster definition set component name:postgresql set component version set component version:postgresql set service versions:12.14.0,12.14.1,12.15.0,12.22.0,14.18.0,14.7.2,14.8.0,15.13.0,15.7.0,16.4.0,16.9.0,17.5.0 set service versions sorted:12.14.0,12.14.1,12.15.0,12.22.0,14.7.2,14.8.0,14.18.0,15.7.0,15.13.0,16.4.0,16.9.0,17.5.0 set postgresql component definition set postgresql component definition postgresql-12 REPORT_COUNT 0:0 set replicas first:2,12.14.0|2,12.14.1|2,12.15.0|2,12.22.0|2,14.7.2|2,14.8.0|2,14.18.0|2,15.7.0|2,15.13.0|2,16.4.0|2,16.9.0|2,17.5.0 set replicas third:2,12.14.0 set replicas fourth:2,12.14.0 set minimum cmpv service version set minimum cmpv service version replicas:2,12.14.0 REPORT_COUNT:1 CLUSTER_TOPOLOGY:replication topology replication found in cluster definition postgresql LIMIT_CPU:0.1 LIMIT_MEMORY:0.5 storage size: 3 No resources found in ns-yztjr namespace. termination_policy:WipeOut create 2 replica WipeOut postgresql cluster check cluster version check cluster definition check component definition set component definition by component version check cmpd by labels set component definition1: postgresql-12 by component version:postgresql apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: postgres-ywrmpr namespace: ns-yztjr spec: clusterDefinitionRef: postgresql topology: replication terminationPolicy: WipeOut componentSpecs: - name: postgresql serviceVersion: 12.14.0 replicas: 2 resources: requests: cpu: 100m memory: 0.5Gi limits: cpu: 100m memory: 0.5Gi volumeClaimTemplates: - name: data spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 3Gi `kubectl apply -f test_create_postgres-ywrmpr.yaml` cluster.apps.kubeblocks.io/postgres-ywrmpr created apply test_create_postgres-ywrmpr.yaml Success `rm -rf test_create_postgres-ywrmpr.yaml` check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Sep 01,2025 11:23 UTC+0800 clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status: cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 11:23 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 11:23 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl get secrets -l app.kubernetes.io/instance=postgres-ywrmpr` set secret: postgres-ywrmpr-postgresql-account-postgres `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.username***"` `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.password***"` `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.port***"` DB_USERNAME:postgres;DB_PASSWORD:8sv2A053Oz;DB_PORT:5432;DB_DATABASE:postgres check pod postgres-ywrmpr-postgresql-1 container_name postgresql exist password 8sv2A053Oz check pod postgres-ywrmpr-postgresql-1 container_name pgbouncer exist password 8sv2A053Oz check pod postgres-ywrmpr-postgresql-1 container_name exporter exist password 8sv2A053Oz check pod postgres-ywrmpr-postgresql-1 container_name lorry exist password 8sv2A053Oz check pod postgres-ywrmpr-postgresql-1 container_name config-manager exist password 8sv2A053Oz No container logs contain secret password. describe cluster `kbcli cluster describe postgres-ywrmpr --namespace ns-yztjr ` Name: postgres-ywrmpr Created Time: Sep 01,2025 11:23 UTC+0800 NAMESPACE CLUSTER-DEFINITION VERSION STATUS TERMINATION-POLICY ns-yztjr postgresql Running WipeOut Endpoints: COMPONENT MODE INTERNAL EXTERNAL postgresql ReadWrite postgres-ywrmpr-postgresql-postgresql.ns-yztjr.svc.cluster.local:5432 postgres-ywrmpr-postgresql-postgresql.ns-yztjr.svc.cluster.local:6432 Topology: COMPONENT INSTANCE ROLE STATUS AZ NODE CREATED-TIME postgresql postgres-ywrmpr-postgresql-0 secondary Running 0 aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 11:23 UTC+0800 postgresql postgres-ywrmpr-postgresql-1 primary Running 0 aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 11:23 UTC+0800 Resources Allocation: COMPONENT DEDICATED CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS postgresql false 100m / 100m 512Mi / 512Mi data:3Gi default Images: COMPONENT TYPE IMAGE postgresql docker.io/apecloud/spilo:12.14.0-pgvector-v0.6.1 Data Protection: BACKUP-REPO AUTO-BACKUP BACKUP-SCHEDULE BACKUP-METHOD BACKUP-RETENTION RECOVERABLE-TIME Show cluster events: kbcli cluster list-events -n ns-yztjr postgres-ywrmpr `kbcli cluster label postgres-ywrmpr app.kubernetes.io/instance- --namespace ns-yztjr ` label "app.kubernetes.io/instance" not found. `kbcli cluster label postgres-ywrmpr app.kubernetes.io/instance=postgres-ywrmpr --namespace ns-yztjr ` `kbcli cluster label postgres-ywrmpr --list --namespace ns-yztjr ` NAME NAMESPACE LABELS postgres-ywrmpr ns-yztjr app.kubernetes.io/instance=postgres-ywrmpr clusterdefinition.kubeblocks.io/name=postgresql clusterversion.kubeblocks.io/name= label cluster app.kubernetes.io/instance=postgres-ywrmpr Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=postgres-ywrmpr --namespace ns-yztjr ` `kbcli cluster label postgres-ywrmpr --list --namespace ns-yztjr ` NAME NAMESPACE LABELS postgres-ywrmpr ns-yztjr app.kubernetes.io/instance=postgres-ywrmpr case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=postgresql clusterversion.kubeblocks.io/name= label cluster case.name=kbcli.test1 Success `kbcli cluster label postgres-ywrmpr case.name=kbcli.test2 --overwrite --namespace ns-yztjr ` `kbcli cluster label postgres-ywrmpr --list --namespace ns-yztjr ` NAME NAMESPACE LABELS postgres-ywrmpr ns-yztjr app.kubernetes.io/instance=postgres-ywrmpr case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=postgresql clusterversion.kubeblocks.io/name= label cluster case.name=kbcli.test2 Success `kbcli cluster label postgres-ywrmpr case.name- --namespace ns-yztjr ` `kbcli cluster label postgres-ywrmpr --list --namespace ns-yztjr ` NAME NAMESPACE LABELS postgres-ywrmpr ns-yztjr app.kubernetes.io/instance=postgres-ywrmpr clusterdefinition.kubeblocks.io/name=postgresql clusterversion.kubeblocks.io/name= delete cluster label case.name Success cluster connect `echo 'create extension vector;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr --namespace ns-yztjr ` Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file CREATE EXTENSION Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file List of installed extensions Name | Version | Schema | Description --------------------+---------+------------+----------------------------------------------------------- file_fdw | 1.0 | public | foreign-data wrapper for flat file access pg_auth_mon | 1.1 | public | monitor connection attempts per user pg_cron | 1.5 | pg_catalog | Job scheduler for PostgreSQL pg_stat_kcache | 2.2.3 | public | Kernel statistics gathering pg_stat_statements | 1.7 | public | track execution statistics of all SQL statements executed plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language plpython3u | 1.0 | pg_catalog | PL/Python3U untrusted procedural language set_user | 3.0 | public | similar to SET ROLE but with added logging vector | 0.6.1 | public | vector data type and ivfflat and hnsw access methods (9 rows) `echo 'show max_connections;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` Unable to use a TTY - input is not a terminal or the right kind of file Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) max_connections ----------------- 56 (1 row) connect cluster Success set max_connections to 56 insert batch data by db client Error from server (NotFound): pods "test-db-client-executionloop-postgres-ywrmpr" not found DB_CLIENT_BATCH_DATA_COUNT: `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-executionloop-postgres-ywrmpr --namespace ns-yztjr ` Error from server (NotFound): pods "test-db-client-executionloop-postgres-ywrmpr" not found Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): pods "test-db-client-executionloop-postgres-ywrmpr" not found `kubectl get secrets -l app.kubernetes.io/instance=postgres-ywrmpr` set secret: postgres-ywrmpr-postgresql-account-postgres `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.username***"` `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.password***"` `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.port***"` DB_USERNAME:postgres;DB_PASSWORD:8sv2A053Oz;DB_PORT:5432;DB_DATABASE:postgres apiVersion: v1 kind: Pod metadata: name: test-db-client-executionloop-postgres-ywrmpr namespace: ns-yztjr spec: containers: - name: test-dbclient imagePullPolicy: IfNotPresent image: docker.io/apecloud/dbclient:test args: - "--host" - "postgres-ywrmpr-postgresql-postgresql.ns-yztjr.svc.cluster.local" - "--user" - "postgres" - "--password" - "8sv2A053Oz" - "--port" - "5432" - "--dbtype" - "postgresql" - "--test" - "executionloop" - "--duration" - "60" - "--interval" - "1" restartPolicy: Never `kubectl apply -f test-db-client-executionloop-postgres-ywrmpr.yaml` pod/test-db-client-executionloop-postgres-ywrmpr created apply test-db-client-executionloop-postgres-ywrmpr.yaml Success `rm -rf test-db-client-executionloop-postgres-ywrmpr.yaml` check pod status pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 5s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 9s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 15s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 20s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 25s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 30s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 35s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 40s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 45s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 51s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 56s pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 1/1 Running 0 61s check pod test-db-client-executionloop-postgres-ywrmpr status done pod_status:NAME READY STATUS RESTARTS AGE test-db-client-executionloop-postgres-ywrmpr 0/1 Completed 0 66s check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 11:23 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 11:23 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done --host postgres-ywrmpr-postgresql-postgresql.ns-yztjr.svc.cluster.local --user postgres --password 8sv2A053Oz --port 5432 --dbtype postgresql --test executionloop --duration 60 --interval 1 SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider] WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.postgresql.jdbc.TimestampUtils (file:/app/oneclient-1.0-all.jar) to field java.util.TimeZone.defaultTimeZone WARNING: Please consider reporting this to the maintainers of org.postgresql.jdbc.TimestampUtils WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Execution loop start: create databases executions_loop CREATE DATABASE executions_loop; reconnect connection executions_loop drop table executions_loop_table DROP TABLE IF EXISTS executions_loop_table; create table executions_loop_table CREATE TABLE IF NOT EXISTS executions_loop_table (id SERIAL PRIMARY KEY, value TEXT, tinyint_col SMALLINT, smallint_col SMALLINT, integer_col INTEGER, bigint_col BIGINT, real_col REAL, double_col DOUBLE PRECISION, numeric_col NUMERIC(10, 2), date_col DATE, time_col TIME, timestamp_col TIMESTAMP, timestamptz_col TIMESTAMP WITH TIME ZONE, interval_col INTERVAL, boolean_col BOOLEAN, char_col CHAR(10), varchar_col VARCHAR(255), text_col TEXT, bytea_col BYTEA, uuid_col UUID, json_col JSON, jsonb_col JSONB, xml_col XML, enum_col VARCHAR(10) CHECK (enum_col IN ('Option1', 'Option2', 'Option3')), set_col VARCHAR(255) CHECK (set_col IN ('Value1', 'Value2', 'Value3')), int_array_col INTEGER[], text_array_col TEXT[], point_col POINT, line_col LINE, lseg_col LSEG, box_col BOX, path_col PATH, polygon_col POLYGON, circle_col CIRCLE, cidr_col CIDR, inet_col INET, macaddr_col MACADDR, macaddr8_col MACADDR8, bit_col BIT(8), bit_var_col BIT VARYING(8), varbit_col BIT VARYING(8), money_col MONEY, oid_col OID, regproc_col REGPROC, regprocedure_col REGPROCEDURE, regoper_col REGOPER, regoperator_col REGOPERATOR, regclass_col REGCLASS, regtype_col REGTYPE, regrole_col REGROLE, regnamespace_col REGNAMESPACE, regconfig_col REGCONFIG, regdictionary_col REGDICTIONARY ); Execution loop start:INSERT INTO executions_loop_table (value, tinyint_col, smallint_col, integer_col, bigint_col, real_col, double_col, numeric_col, date_col, time_col, timestamp_col, timestamptz_col, interval_col, boolean_col, char_col, varchar_col, text_col, bytea_col, uuid_col, json_col, jsonb_col, xml_col, enum_col, set_col, int_array_col, text_array_col, point_col, line_col, lseg_col, box_col, path_col, polygon_col, circle_col, cidr_col, inet_col, macaddr_col, macaddr8_col, bit_col, bit_var_col, varbit_col, money_col, oid_col, regproc_col, regprocedure_col, regoper_col, regoperator_col, regclass_col, regtype_col, regrole_col, regnamespace_col, regconfig_col, regdictionary_col) VALUES ('executions_loop_test_1', 21, 16511, -1557998866, 6540442869989284415, 0.23448157, 0.5874707993168211, 53.236910961887205, '2025-09-01', '03:28:37', '2025-09-01 03:28:37.857', CURRENT_TIMESTAMP, '10 hours 6 minutes 19 seconds', FALSE, 'YC7rDuSJTC', 'o3uO0dBUDamW20zyK30ZCoB8vPm9HuFaWSD8Juk967ms5xcG7CqwPXAbFaPQxZ6fog5Bf19vpzzJfIjyMVZdF1cjrLM8sFpxqBuAM6sHwvPWgcAOyHPLONSFZu9KCj9y4SyxULC9eK8MgVJgkeAnMzXJHnMdm4X6YN1rb4ZL6JSDg83guYYCPf2FHKX6zLasVeffzku9yOPA3tEka4vfJJsRzyO2dQTP2gRMz1d3K8tvF9bv8W0oKqcdcF7Mtj6', 'KXptdyswkNim7em8JQva31DrbU1TJM8nKZZkV6vFpacbBFoXYLT6IRxLZ2SKlHckRFEnNuFZBS4o6v4FVNsgtu8cKLSTKuWIuPVrcTxrD0sKCoYMjlS7wYPT1gGGqP3SZOhrUJTgcpOSfnEl9wkaoDQ0msIk2LJ6nnoETtBIZPHlpQvsA58g5wfRjHae9yzDdYEJ9bKG8ctM0h5CphQCfh1udyfF9Qe7WS0xepZZYxSjvpeWC06eQwgjt2cDzVo', decode('23adb2f9be90b7fa2876', 'hex'), '9dbb5b28-6d10-4f9c-a320-69031cd731fa', '***"key1": "EjWeFSwT2i", "key2": 76***', '***"key1": "wzZUCvP2dm", "key2": 67***', 'bbCatVwl1o42', 'Option1', 'Value1', ARRAY[59, 86, 73], ARRAY['KDAp3TivTC', 'MQ4R6cDUaF', 'wZ3iCdzJER'], '(52.47510624874634, 97.45842694125881)', '***38.608964220445905, 2.4970470416814106, 80.85015666757313***', '[(31.49071212989939, 7.35846035762473), (57.55838992344613, 35.3676771063856)]', '((15.26060429903433, 57.26548089020107), (98.53810861275004, 34.43164956022198))', '((6.593615272631137, 6.246183325417576), (39.374218388200276, 81.7850689124585), (27.54153792341716, 88.19617622777987))', '((36.85396317863885, 24.17287955687022), (29.84379358499274, 51.21307191889861), (47.47745399477936, 36.67338530418892), (96.87758538310294, 98.52200878749414))', '<(44.523591, 93.969417), 7.650716>', '192.168.224.0/24', '192.168.136.115', '08:00:2b:01:02:03', '08:00:2b:01:02:03:04:05', B'10101010', B'10101010', B'10101010', '$852.3720274690764', -367392897, 'acos', abs(1), '#-', +1, 'pg_class', 'integer', 'postgres', 'pg_catalog', 'simple', 'english_stem' ); [ 1s ] executions total: 38 successful: 38 failed: 0 disconnect: 0 [ 2s ] executions total: 136 successful: 136 failed: 0 disconnect: 0 [ 3s ] executions total: 243 successful: 243 failed: 0 disconnect: 0 [ 4s ] executions total: 352 successful: 352 failed: 0 disconnect: 0 [ 5s ] executions total: 454 successful: 454 failed: 0 disconnect: 0 [ 6s ] executions total: 562 successful: 562 failed: 0 disconnect: 0 [ 7s ] executions total: 654 successful: 654 failed: 0 disconnect: 0 [ 8s ] executions total: 736 successful: 736 failed: 0 disconnect: 0 [ 9s ] executions total: 816 successful: 816 failed: 0 disconnect: 0 [ 10s ] executions total: 918 successful: 918 failed: 0 disconnect: 0 [ 11s ] executions total: 1024 successful: 1024 failed: 0 disconnect: 0 [ 12s ] executions total: 1103 successful: 1103 failed: 0 disconnect: 0 [ 13s ] executions total: 1205 successful: 1205 failed: 0 disconnect: 0 [ 14s ] executions total: 1285 successful: 1285 failed: 0 disconnect: 0 [ 15s ] executions total: 1366 successful: 1366 failed: 0 disconnect: 0 [ 16s ] executions total: 1459 successful: 1459 failed: 0 disconnect: 0 [ 17s ] executions total: 1534 successful: 1534 failed: 0 disconnect: 0 [ 18s ] executions total: 1624 successful: 1624 failed: 0 disconnect: 0 [ 19s ] executions total: 1684 successful: 1684 failed: 0 disconnect: 0 [ 20s ] executions total: 1757 successful: 1757 failed: 0 disconnect: 0 [ 21s ] executions total: 1856 successful: 1856 failed: 0 disconnect: 0 [ 22s ] executions total: 1910 successful: 1910 failed: 0 disconnect: 0 [ 23s ] executions total: 1936 successful: 1936 failed: 0 disconnect: 0 [ 24s ] executions total: 2003 successful: 2003 failed: 0 disconnect: 0 [ 25s ] executions total: 2098 successful: 2098 failed: 0 disconnect: 0 [ 26s ] executions total: 2183 successful: 2183 failed: 0 disconnect: 0 [ 27s ] executions total: 2251 successful: 2251 failed: 0 disconnect: 0 [ 28s ] executions total: 2281 successful: 2281 failed: 0 disconnect: 0 [ 29s ] executions total: 2323 successful: 2323 failed: 0 disconnect: 0 [ 30s ] executions total: 2420 successful: 2420 failed: 0 disconnect: 0 [ 31s ] executions total: 2527 successful: 2527 failed: 0 disconnect: 0 [ 32s ] executions total: 2618 successful: 2618 failed: 0 disconnect: 0 [ 33s ] executions total: 2724 successful: 2724 failed: 0 disconnect: 0 [ 34s ] executions total: 2835 successful: 2835 failed: 0 disconnect: 0 [ 35s ] executions total: 2944 successful: 2944 failed: 0 disconnect: 0 [ 36s ] executions total: 3049 successful: 3049 failed: 0 disconnect: 0 [ 37s ] executions total: 3100 successful: 3100 failed: 0 disconnect: 0 [ 38s ] executions total: 3122 successful: 3122 failed: 0 disconnect: 0 [ 39s ] executions total: 3160 successful: 3160 failed: 0 disconnect: 0 [ 40s ] executions total: 3271 successful: 3271 failed: 0 disconnect: 0 [ 41s ] executions total: 3377 successful: 3377 failed: 0 disconnect: 0 [ 42s ] executions total: 3463 successful: 3463 failed: 0 disconnect: 0 [ 43s ] executions total: 3559 successful: 3559 failed: 0 disconnect: 0 [ 44s ] executions total: 3643 successful: 3643 failed: 0 disconnect: 0 [ 45s ] executions total: 3727 successful: 3727 failed: 0 disconnect: 0 [ 46s ] executions total: 3814 successful: 3814 failed: 0 disconnect: 0 [ 47s ] executions total: 3885 successful: 3885 failed: 0 disconnect: 0 [ 48s ] executions total: 3969 successful: 3969 failed: 0 disconnect: 0 [ 49s ] executions total: 4021 successful: 4021 failed: 0 disconnect: 0 [ 50s ] executions total: 4112 successful: 4112 failed: 0 disconnect: 0 [ 51s ] executions total: 4199 successful: 4199 failed: 0 disconnect: 0 [ 52s ] executions total: 4244 successful: 4244 failed: 0 disconnect: 0 [ 53s ] executions total: 4263 successful: 4263 failed: 0 disconnect: 0 [ 54s ] executions total: 4285 successful: 4285 failed: 0 disconnect: 0 [ 55s ] executions total: 4336 successful: 4336 failed: 0 disconnect: 0 [ 56s ] executions total: 4394 successful: 4394 failed: 0 disconnect: 0 [ 57s ] executions total: 4455 successful: 4455 failed: 0 disconnect: 0 [ 58s ] executions total: 4481 successful: 4481 failed: 0 disconnect: 0 [ 59s ] executions total: 4519 successful: 4519 failed: 0 disconnect: 0 [ 60s ] executions total: 4547 successful: 4547 failed: 0 disconnect: 0 Test Result: Total Executions: 4547 Successful Executions: 4547 Failed Executions: 0 Disconnection Counts: 0 Connection Information: Database Type: postgresql Host: postgres-ywrmpr-postgresql-postgresql.ns-yztjr.svc.cluster.local Port: 5432 Database: Table: User: postgres Org: Access Mode: mysql Test Type: executionloop Query: Duration: 60 seconds Interval: 1 seconds DB_CLIENT_BATCH_DATA_COUNT: 4547 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-executionloop-postgres-ywrmpr --namespace ns-yztjr ` pod/test-db-client-executionloop-postgres-ywrmpr patched (no change) Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. pod "test-db-client-executionloop-postgres-ywrmpr" force deleted `echo "DROP TABLE IF EXISTS tmp_table; CREATE TABLE IF NOT EXISTS tmp_table (id INT PRIMARY KEY , value text); INSERT INTO tmp_table (id,value) VALUES (1,'fxsvi');" | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file NOTICE: table "tmp_table" does not exist, skipping DROP TABLE CREATE TABLE INSERT 0 1 add consistent data fxsvi Success `echo "DROP TABLE IF EXISTS tmp_table; CREATE TABLE IF NOT EXISTS tmp_table (id INT PRIMARY KEY , value text); INSERT INTO tmp_table (id,value) VALUES (1,'fxsvi');" | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file ERROR: cannot execute DROP TABLE in a read-only transaction ERROR: cannot execute CREATE TABLE in a read-only transaction ERROR: cannot execute INSERT in a read-only transaction check add consistent data readonly Success cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose postgres-ywrmpr --auto-approve --force=true --type vpc --enable true --components postgresql --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-expose-nddmn created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-expose-nddmn -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr Creating -/- Sep 01,2025 11:29 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 11:23 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 11:23 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 11:29 UTC+0800 check ops status done ops_status:postgres-ywrmpr-expose-nddmn ns-yztjr Expose postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:29 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-expose-nddmn --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-expose-nddmn patched `kbcli cluster delete-ops --name postgres-ywrmpr-expose-nddmn --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-expose-nddmn deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart postgres-ywrmpr --auto-approve --force=true --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-restart-7ntpm created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-restart-7ntpm -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-restart-7ntpm ns-yztjr Restart postgres-ywrmpr postgresql Creating -/- Sep 01,2025 11:31 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 11:34 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-restart-7ntpm ns-yztjr Restart postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:31 UTC+0800 check ops status done ops_status:postgres-ywrmpr-restart-7ntpm ns-yztjr Restart postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:31 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-restart-7ntpm --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-restart-7ntpm patched `kbcli cluster delete-ops --name postgres-ywrmpr-restart-7ntpm --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-restart-7ntpm deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cluster update terminationPolicy WipeOut `kbcli cluster update postgres-ywrmpr --termination-policy=WipeOut --namespace ns-yztjr ` cluster.apps.kubeblocks.io/postgres-ywrmpr updated (no change) check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 11:34 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl get backupschedule -l app.kubernetes.io/instance=postgres-ywrmpr ` `kubectl get backupschedule postgres-ywrmpr-postgresql-backup-schedule -ojsonpath='***.spec.schedules[*].backupMethod***' ` backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched cluster pg-basebackup backup `kubectl get backuprepo backuprepo-kbcli-test -o jsonpath="***.spec.credential.name***"` `kubectl get backuprepo backuprepo-kbcli-test -o jsonpath="***.spec.credential.namespace***"` `kubectl get secrets kb-backuprepo-bxwnt -n kb-hmwej -o jsonpath="***.data.accessKeyId***"` `kubectl get secrets kb-backuprepo-bxwnt -n kb-hmwej -o jsonpath="***.data.secretAccessKey***"` KUBEBLOCKS NAMESPACE:kb-hmwej get kubeblocks namespace done `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-hmwej -o jsonpath="***.items[0].data.root-user***"` `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-hmwej -o jsonpath="***.items[0].data.root-password***"` minio_user:kbclitest,minio_password:kbclitest,minio_endpoint:kbcli-test-minio.kb-hmwej.svc.cluster.local:9000 list minio bucket kbcli-test `echo 'mc config host add minioserver http://kbcli-test-minio.kb-hmwej.svc.cluster.local:9000 kbclitest kbclitest;mc ls minioserver' | kubectl exec -it kbcli-test-minio-669d87677b-sp687 --namespace kb-hmwej -- bash` Unable to use a TTY - input is not a terminal or the right kind of file list minio bucket done default backuprepo:backuprepo-kbcli-test exists `kbcli cluster backup postgres-ywrmpr --method pg-basebackup --namespace ns-yztjr ` Backup backup-ns-yztjr-postgres-ywrmpr-20250901113608 created successfully, you can view the progress: kbcli cluster list-backups --name=backup-ns-yztjr-postgres-ywrmpr-20250901113608 -n ns-yztjr check backup status `kbcli cluster list-backups postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE SOURCE-CLUSTER METHOD STATUS TOTAL-SIZE DURATION CREATE-TIME COMPLETION-TIME EXPIRATION 49aa172b-postgres-ywrmpr-postg-archive-wal ns-yztjr postgres-ywrmpr archive-wal Running(AvailablePods: 0) Sep 01,2025 11:36 UTC+0800 backup_status:postgres-ywrmpr-pg-basebackup-Running backup_status:postgres-ywrmpr-pg-basebackup-Running backup_status:postgres-ywrmpr-pg-basebackup-Running check backup status done backup_status:backup-ns-yztjr-postgres-ywrmpr-20250901113608 ns-yztjr postgres-ywrmpr pg-basebackup Completed 13075549 10s Sep 01,2025 11:36 UTC+0800 Sep 01,2025 11:36 UTC+0800 `create table if not exists msg(id SERIAL PRIMARY KEY, msg text, time timestamp);insert into msg (msg, time) values ('kbcli-test-data-ywrmpr0', now());` Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file CREATE TABLE INSERT 0 1 `insert into msg (msg, time) values ('kbcli-test-data-ywrmpr1', now());` Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file INSERT 0 1 Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file pg_switch_wal --------------- 0/47E6E10 (1 row) `insert into msg (msg, time) values ('kbcli-test-data-ywrmpr2', now());` Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file INSERT 0 1 Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file pg_switch_wal --------------- 0/5000108 (1 row) checking recoverable time 1 recoverable time:Sep 01,2025 11:36:27 UTC+0800 `insert into msg (msg, time) values ('kbcli-test-data-ywrmpr4', now());` Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file INSERT 0 1 Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file pg_switch_wal --------------- 0/6000140 (1 row) check recoverable time 1 done recoverable time:Sep 01,2025 11:36:35 UTC+0800 cluster restore-to-time backup Error from server (NotFound): opsrequests.apps.kubeblocks.io "postgres-ywrmpr-backup" not found `kbcli cluster restore postgres-ywrmpr-backup --backup 49aa172b-postgres-ywrmpr-postg-archive-wal --restore-to-time "Sep 01,2025 11:36:35 UTC+0800" --namespace ns-yztjr ` Cluster postgres-ywrmpr-backup created check cluster status `kbcli cluster list postgres-ywrmpr-backup --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr-backup ns-yztjr postgresql WipeOut Sep 01,2025 11:36 UTC+0800 cluster_status: cluster_status: cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status: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 postgres-ywrmpr-backup --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-backup-postgresql-0 ns-yztjr postgres-ywrmpr-backup postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 11:37 UTC+0800 postgres-ywrmpr-backup-postgresql-1 ns-yztjr postgres-ywrmpr-backup postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:37 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-backup-postgresql-1;secondary: postgres-ywrmpr-backup-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr` check cluster connect done `select * from msg;` Unable to use a TTY - input is not a terminal or the right kind of file Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) id | msg | time ----+-------------------------+---------------------------- 1 | kbcli-test-data-ywrmpr0 | 2025-09-01 03:36:25.322511 2 | kbcli-test-data-ywrmpr1 | 2025-09-01 03:36:27.613578 (2 rows) Point-In-Time Recovery Success `echo 'DROP TABLE msg;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file DROP TABLE `kubectl get backupschedule -l app.kubernetes.io/instance=postgres-ywrmpr ` `kubectl get backupschedule postgres-ywrmpr-postgresql-backup-schedule -ojsonpath='***.spec.schedules[*].backupMethod***' ` backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) cluster connect `echo 'create extension vector;' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr --namespace ns-yztjr ` Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file ERROR: extension "vector" already exists Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file List of installed extensions Name | Version | Schema | Description --------------------+---------+------------+----------------------------------------------------------- file_fdw | 1.0 | public | foreign-data wrapper for flat file access pg_auth_mon | 1.1 | public | monitor connection attempts per user pg_cron | 1.5 | pg_catalog | Job scheduler for PostgreSQL pg_stat_kcache | 2.2.3 | public | Kernel statistics gathering pg_stat_statements | 1.7 | public | track execution statistics of all SQL statements executed plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language plpython3u | 1.0 | pg_catalog | PL/Python3U untrusted procedural language set_user | 3.0 | public | similar to SET ROLE but with added logging vector | 0.6.1 | public | vector data type and ivfflat and hnsw access methods (9 rows) `echo 'show max_connections;' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr ` Unable to use a TTY - input is not a terminal or the right kind of file Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) max_connections ----------------- 56 (1 row) connect cluster Success set max_connections to 56 delete cluster postgres-ywrmpr-backup `kbcli cluster delete postgres-ywrmpr-backup --auto-approve --namespace ns-yztjr ` Cluster postgres-ywrmpr-backup deleted pod_info:postgres-ywrmpr-backup-postgresql-0 5/5 Running 0 6m29s postgres-ywrmpr-backup-postgresql-1 5/5 Running 0 6m29s pod_info:postgres-ywrmpr-backup-postgresql-1 4/5 Terminating 0 6m49s No resources found in ns-yztjr namespace. delete cluster pod done No resources found in ns-yztjr namespace. check cluster resource non-exist OK: pvc No resources found in ns-yztjr namespace. delete cluster done No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. cluster delete backup `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge backups 49aa172b-postgres-ywrmpr-postg-archive-wal --namespace ns-yztjr ` backup.dataprotection.kubeblocks.io/49aa172b-postgres-ywrmpr-postg-archive-wal patched `kbcli cluster delete-backup postgres-ywrmpr --name 49aa172b-postgres-ywrmpr-postg-archive-wal --force --auto-approve --namespace ns-yztjr ` Backup 49aa172b-postgres-ywrmpr-postg-archive-wal deleted `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge backups backup-ns-yztjr-postgres-ywrmpr-20250901113608 --namespace ns-yztjr ` backup.dataprotection.kubeblocks.io/backup-ns-yztjr-postgres-ywrmpr-20250901113608 patched `kbcli cluster delete-backup postgres-ywrmpr --name backup-ns-yztjr-postgres-ywrmpr-20250901113608 --force --auto-approve --namespace ns-yztjr ` Backup backup-ns-yztjr-postgres-ywrmpr-20250901113608 deleted cmpv upgrade service version:2,12.14.0|2,12.14.1|2,12.15.0|2,12.22.0|2,14.7.2|2,14.8.0|2,14.18.0|2,15.7.0|2,15.13.0|2,16.4.0|2,16.9.0|2,17.5.0 set latest cmpv service version latest service version:12.22.0 cmpv service version upgrade and downgrade upgrade from:12.14.0 to service version:12.22.0 cluster upgrade apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: postgres-ywrmpr-upgrade-cmpv- namespace: ns-yztjr spec: clusterName: postgres-ywrmpr upgrade: components: - componentName: postgresql serviceVersion: 12.22.0 type: Upgrade check cluster status before ops cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 `kubectl create -f test_ops_cluster_postgres-ywrmpr.yaml` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-mhjd8 created create test_ops_cluster_postgres-ywrmpr.yaml Success `rm -rf test_ops_cluster_postgres-ywrmpr.yaml` check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-mhjd8 ns-yztjr Upgrade postgres-ywrmpr Pending -/- Sep 01,2025 11:46 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-mhjd8 ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:46 UTC+0800 check ops status done ops_status:postgres-ywrmpr-upgrade-cmpv-mhjd8 ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:46 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-upgrade-cmpv-mhjd8 --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-mhjd8 patched `kbcli cluster delete-ops --name postgres-ywrmpr-upgrade-cmpv-mhjd8 --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-upgrade-cmpv-mhjd8 deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success downgrade from:12.22.0 to service version:12.14.0 cluster upgrade apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: postgres-ywrmpr-upgrade-cmpv- namespace: ns-yztjr spec: clusterName: postgres-ywrmpr upgrade: components: - componentName: postgresql serviceVersion: 12.14.0 type: Upgrade check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_postgres-ywrmpr.yaml` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-vl68w created create test_ops_cluster_postgres-ywrmpr.yaml Success `rm -rf test_ops_cluster_postgres-ywrmpr.yaml` check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-vl68w ns-yztjr Upgrade postgres-ywrmpr Pending -/- Sep 01,2025 11:49 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-vl68w ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:49 UTC+0800 check ops status done ops_status:postgres-ywrmpr-upgrade-cmpv-vl68w ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:49 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-upgrade-cmpv-vl68w --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-vl68w patched `kbcli cluster delete-ops --name postgres-ywrmpr-upgrade-cmpv-vl68w --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-upgrade-cmpv-vl68w deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success upgrade from:12.14.0 to service version:12.14.1 cluster upgrade apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: postgres-ywrmpr-upgrade-cmpv- namespace: ns-yztjr spec: clusterName: postgres-ywrmpr upgrade: components: - componentName: postgresql serviceVersion: 12.14.1 type: Upgrade check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_postgres-ywrmpr.yaml` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-bwwgb created create test_ops_cluster_postgres-ywrmpr.yaml Success `rm -rf test_ops_cluster_postgres-ywrmpr.yaml` check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-bwwgb ns-yztjr Upgrade postgres-ywrmpr Creating -/- Sep 01,2025 11:51 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-bwwgb ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:51 UTC+0800 check ops status done ops_status:postgres-ywrmpr-upgrade-cmpv-bwwgb ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:51 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-upgrade-cmpv-bwwgb --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-bwwgb patched `kbcli cluster delete-ops --name postgres-ywrmpr-upgrade-cmpv-bwwgb --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-upgrade-cmpv-bwwgb deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success upgrade from:12.14.1 to service version:12.22.0 cluster upgrade apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: postgres-ywrmpr-upgrade-cmpv- namespace: ns-yztjr spec: clusterName: postgres-ywrmpr upgrade: components: - componentName: postgresql serviceVersion: 12.22.0 type: Upgrade check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_postgres-ywrmpr.yaml` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-cxjjb created create test_ops_cluster_postgres-ywrmpr.yaml Success `rm -rf test_ops_cluster_postgres-ywrmpr.yaml` check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-cxjjb ns-yztjr Upgrade postgres-ywrmpr Pending -/- Sep 01,2025 11:54 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-cxjjb ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:54 UTC+0800 check ops status done ops_status:postgres-ywrmpr-upgrade-cmpv-cxjjb ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:54 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-upgrade-cmpv-cxjjb --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-cxjjb patched `kbcli cluster delete-ops --name postgres-ywrmpr-upgrade-cmpv-cxjjb --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-upgrade-cmpv-cxjjb deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success downgrade from:12.22.0 to service version:12.14.1 cluster upgrade apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: postgres-ywrmpr-upgrade-cmpv- namespace: ns-yztjr spec: clusterName: postgres-ywrmpr upgrade: components: - componentName: postgresql serviceVersion: 12.14.1 type: Upgrade check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_postgres-ywrmpr.yaml` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-m4gjw created create test_ops_cluster_postgres-ywrmpr.yaml Success `rm -rf test_ops_cluster_postgres-ywrmpr.yaml` check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-m4gjw ns-yztjr Upgrade postgres-ywrmpr Pending -/- Sep 01,2025 11:57 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-m4gjw ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:57 UTC+0800 check ops status done ops_status:postgres-ywrmpr-upgrade-cmpv-m4gjw ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:57 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-upgrade-cmpv-m4gjw --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-m4gjw patched `kbcli cluster delete-ops --name postgres-ywrmpr-upgrade-cmpv-m4gjw --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-upgrade-cmpv-m4gjw deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success upgrade from:12.14.1 to service version:12.15.0 cluster upgrade apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: postgres-ywrmpr-upgrade-cmpv- namespace: ns-yztjr spec: clusterName: postgres-ywrmpr upgrade: components: - componentName: postgresql serviceVersion: 12.15.0 type: Upgrade check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_postgres-ywrmpr.yaml` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-mm87j created create test_ops_cluster_postgres-ywrmpr.yaml Success `rm -rf test_ops_cluster_postgres-ywrmpr.yaml` check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-mm87j ns-yztjr Upgrade postgres-ywrmpr Creating -/- Sep 01,2025 11:59 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-mm87j ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:59 UTC+0800 check ops status done ops_status:postgres-ywrmpr-upgrade-cmpv-mm87j ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 11:59 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-upgrade-cmpv-mm87j --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-mm87j patched `kbcli cluster delete-ops --name postgres-ywrmpr-upgrade-cmpv-mm87j --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-upgrade-cmpv-mm87j deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success upgrade from:12.15.0 to service version:12.22.0 cluster upgrade apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: postgres-ywrmpr-upgrade-cmpv- namespace: ns-yztjr spec: clusterName: postgres-ywrmpr upgrade: components: - componentName: postgresql serviceVersion: 12.22.0 type: Upgrade check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_postgres-ywrmpr.yaml` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-4vdjt created create test_ops_cluster_postgres-ywrmpr.yaml Success `rm -rf test_ops_cluster_postgres-ywrmpr.yaml` check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-4vdjt ns-yztjr Upgrade postgres-ywrmpr Creating -/- Sep 01,2025 12:02 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-4vdjt ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 12:02 UTC+0800 check ops status done ops_status:postgres-ywrmpr-upgrade-cmpv-4vdjt ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 12:02 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-upgrade-cmpv-4vdjt --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-4vdjt patched `kbcli cluster delete-ops --name postgres-ywrmpr-upgrade-cmpv-4vdjt --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-upgrade-cmpv-4vdjt deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success downgrade from:12.22.0 to service version:12.15.0 cluster upgrade apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: postgres-ywrmpr-upgrade-cmpv- namespace: ns-yztjr spec: clusterName: postgres-ywrmpr upgrade: components: - componentName: postgresql serviceVersion: 12.15.0 type: Upgrade check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_postgres-ywrmpr.yaml` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-c6x8h created create test_ops_cluster_postgres-ywrmpr.yaml Success `rm -rf test_ops_cluster_postgres-ywrmpr.yaml` check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-c6x8h ns-yztjr Upgrade postgres-ywrmpr Creating -/- Sep 01,2025 12:04 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-c6x8h ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 12:04 UTC+0800 check ops status done ops_status:postgres-ywrmpr-upgrade-cmpv-c6x8h ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 12:04 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-upgrade-cmpv-c6x8h --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-c6x8h patched `kbcli cluster delete-ops --name postgres-ywrmpr-upgrade-cmpv-c6x8h --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-upgrade-cmpv-c6x8h deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cmpv service version downgrade downgrade from:12.15.0 to service version:12.14.0 cluster upgrade apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: postgres-ywrmpr-upgrade-cmpv- namespace: ns-yztjr spec: clusterName: postgres-ywrmpr upgrade: components: - componentName: postgresql serviceVersion: 12.14.0 type: Upgrade check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_postgres-ywrmpr.yaml` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-vj7cr created create test_ops_cluster_postgres-ywrmpr.yaml Success `rm -rf test_ops_cluster_postgres-ywrmpr.yaml` check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-vj7cr ns-yztjr Upgrade postgres-ywrmpr Creating -/- Sep 01,2025 12:07 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-upgrade-cmpv-vj7cr ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 12:07 UTC+0800 check ops status done ops_status:postgres-ywrmpr-upgrade-cmpv-vj7cr ns-yztjr Upgrade postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 12:07 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-upgrade-cmpv-vj7cr --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-upgrade-cmpv-vj7cr patched `kbcli cluster delete-ops --name postgres-ywrmpr-upgrade-cmpv-vj7cr --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-upgrade-cmpv-vj7cr deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover fullcpu check cluster status before cluster-failover-fullcpu check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-fullcpu-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" not found Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-fullcpu-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: StressChaos metadata: name: test-chaos-mesh-fullcpu-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-1 mode: all stressors: cpu: workers: 100 load: 100 duration: 2m `kubectl apply -f test-chaos-mesh-fullcpu-postgres-ywrmpr.yaml` stresschaos.chaos-mesh.org/test-chaos-mesh-fullcpu-postgres-ywrmpr created apply test-chaos-mesh-fullcpu-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-fullcpu-postgres-ywrmpr.yaml` fullcpu chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-fullcpu-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" force deleted Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-fullcpu-postgres-ywrmpr" not found check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover fullcpu Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover dnsrandom check cluster status before cluster-failover-dnsrandom check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnsrandom-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" not found Error from server (NotFound): dnschaos.chaos-mesh.org "test-chaos-mesh-dnsrandom-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: DNSChaos metadata: name: test-chaos-mesh-dnsrandom-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-1 mode: all action: random duration: 2m `kubectl apply -f test-chaos-mesh-dnsrandom-postgres-ywrmpr.yaml` dnschaos.chaos-mesh.org/test-chaos-mesh-dnsrandom-postgres-ywrmpr created apply test-chaos-mesh-dnsrandom-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-dnsrandom-postgres-ywrmpr.yaml` dnsrandom chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnsrandom-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" force deleted dnschaos.chaos-mesh.org/test-chaos-mesh-dnsrandom-postgres-ywrmpr patched check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover dnsrandom Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover networklossover check cluster status before cluster-failover-networklossover check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networklossover-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networklossover-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networklossover-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-1 mode: all action: loss loss: loss: '100' correlation: '100' direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networklossover-postgres-ywrmpr.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networklossover-postgres-ywrmpr created apply test-chaos-mesh-networklossover-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-networklossover-postgres-ywrmpr.yaml` networklossover chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networklossover-postgres-ywrmpr --namespace ns-yztjr ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. networkchaos.chaos-mesh.org "test-chaos-mesh-networklossover-postgres-ywrmpr" force deleted Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networklossover-postgres-ywrmpr" not found check failover pod name failover pod name:postgres-ywrmpr-postgresql-0 failover networklossover Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory Is the server running locally and accepting connections on that socket? command terminated with exit code 2 checking cluster readonly data consistent... check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover podfailure check cluster status before cluster-failover-podfailure check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge PodChaos test-chaos-mesh-podfailure-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" not found Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podfailure-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: PodChaos metadata: name: test-chaos-mesh-podfailure-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-0 mode: all action: pod-failure duration: 2m `kubectl apply -f test-chaos-mesh-podfailure-postgres-ywrmpr.yaml` podchaos.chaos-mesh.org/test-chaos-mesh-podfailure-postgres-ywrmpr created apply test-chaos-mesh-podfailure-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-podfailure-postgres-ywrmpr.yaml` podfailure chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Abnormal Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Abnormal cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge PodChaos test-chaos-mesh-podfailure-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" force deleted Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podfailure-postgres-ywrmpr" not found check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover podfailure Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover networkduplicate check cluster status before cluster-failover-networkduplicate check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkduplicate-postgres-ywrmpr --namespace ns-yztjr ` Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkduplicate-postgres-ywrmpr" not found Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkduplicate-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-1 mode: all action: duplicate duplicate: duplicate: '100' correlation: '100' direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkduplicate-postgres-ywrmpr.yaml` Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkduplicate-postgres-ywrmpr" not found networkchaos.chaos-mesh.org/test-chaos-mesh-networkduplicate-postgres-ywrmpr created apply test-chaos-mesh-networkduplicate-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-networkduplicate-postgres-ywrmpr.yaml` networkduplicate chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkduplicate-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" force deleted networkchaos.chaos-mesh.org/test-chaos-mesh-networkduplicate-postgres-ywrmpr patched check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover networkduplicate Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover dnserror check cluster status before cluster-failover-dnserror check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnserror-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" not found Error from server (NotFound): dnschaos.chaos-mesh.org "test-chaos-mesh-dnserror-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: DNSChaos metadata: name: test-chaos-mesh-dnserror-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-1 mode: all action: error duration: 2m `kubectl apply -f test-chaos-mesh-dnserror-postgres-ywrmpr.yaml` dnschaos.chaos-mesh.org/test-chaos-mesh-dnserror-postgres-ywrmpr created apply test-chaos-mesh-dnserror-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-dnserror-postgres-ywrmpr.yaml` dnserror chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 11:32 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 100m / 100m 512Mi / 512Mi data:3Gi aks-default-25371978-vmss000000/10.224.0.4 Sep 01,2025 11:44 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge DNSChaos test-chaos-mesh-dnserror-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" force deleted dnschaos.chaos-mesh.org/test-chaos-mesh-dnserror-postgres-ywrmpr patched check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover dnserror Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cluster vscale check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale postgres-ywrmpr --auto-approve --force=true --components postgresql --cpu 200m --memory 0.6Gi --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-verticalscaling-8bpwj created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-verticalscaling-8bpwj -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-verticalscaling-8bpwj ns-yztjr VerticalScaling postgres-ywrmpr postgresql Pending -/- Sep 01,2025 12:24 UTC+0800 ops_status:postgres-ywrmpr-verticalscaling-8bpwj ns-yztjr VerticalScaling postgres-ywrmpr postgresql Creating -/- Sep 01,2025 12:24 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:24 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 12:25 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-verticalscaling-8bpwj ns-yztjr VerticalScaling postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 12:24 UTC+0800 check ops status done ops_status:postgres-ywrmpr-verticalscaling-8bpwj ns-yztjr VerticalScaling postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 12:24 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-verticalscaling-8bpwj --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-verticalscaling-8bpwj patched `kbcli cluster delete-ops --name postgres-ywrmpr-verticalscaling-8bpwj --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-verticalscaling-8bpwj deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cluster update monitor cluster does not need to check monitor currently check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:24 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 12:25 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done test failover drainnode check cluster status before cluster-failover-drainnode check cluster status done cluster_status:Running check node drain check node drain success kubectl get pod postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -o jsonpath='***.spec.nodeName***' get node name:aks-cicdamdpool-38368475-vmss000006 success check if multiple pods are on the same node kubectl get pod postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -o jsonpath='***.spec.nodeName***' get node name:aks-cicdamdpool-38368475-vmss000000 success kubectl drain aks-cicdamdpool-38368475-vmss000006 --delete-emptydir-data --ignore-daemonsets --force --grace-period 0 --timeout 60s node/aks-cicdamdpool-38368475-vmss000006 cordoned Warning: ignoring DaemonSet-managed Pods: chaos-mesh/chaos-daemon-vs6fn, kb-hmwej/kb-addon-apecloud-otel-collector-dcrnn, kube-system/azure-cns-lfghc, kube-system/azure-ip-masq-agent-rl2nt, kube-system/cloud-node-manager-vsbz9, kube-system/csi-azuredisk-node-kqwnx, kube-system/csi-azurefile-node-7w5bm, kube-system/kube-proxy-wrvb2; deleting Pods that declare no controller: ns-hrbfe/kafka-esbuyt-kafka-producer evicting pod chaos-mesh/chaos-controller-manager-675887849-l8l56 evicting pod ns-fkhrb/damengdb-tkwqqh-dmdb-1 evicting pod ns-fkhrb/damengdb-tkwqqh-dmdb-2 evicting pod ns-yztjr/postgres-ywrmpr-postgresql-0 evicting pod chaos-mesh/chaos-dashboard-7b866cc765-tf2t7 evicting pod chaos-mesh/chaos-controller-manager-675887849-f24b7 evicting pod chaos-mesh/chaos-dns-server-cd7c67cc5-phlmw evicting pod kb-hmwej/kb-addon-grafana-77bd68f6b8-65d59 evicting pod chaos-mesh/chaos-controller-manager-675887849-jnxpw evicting pod ns-hrbfe/kafka-esbuyt-kafka-broker-1 evicting pod kb-hmwej/keda-operator-metrics-apiserver-7895dbb47b-6dplq evicting pod kb-hmwej/kubeblocks-54b68fc4f9-qzsqk evicting pod ns-rxzwd/redis-lyqvhu-redis-0 evicting pod kube-system/konnectivity-agent-867755898d-xj98n evicting pod kb-hmwej/kb-addon-prometheus-server-0 evicting pod ns-hrbfe/kafka-esbuyt-kafka-producer evicting pod ns-hrbfe/kafka-esbuyt-kafka-exporter-0 evicting pod kb-hmwej/keda-admission-webhooks-57ffdc99c4-r76s8 evicting pod ns-hrbfe/kafka-esbuyt-kafka-zookeeper-0 evicting pod kube-system/metrics-server-6b88d9f9c9-sfnzl evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 evicting pod ns-hrbfe/kafka-esbuyt-kafka-zookeeper-2 evicting pod ns-sfkux/apemysql-txrgwo-mysql-1 evicting pod kb-hmwej/keda-operator-68b7db459f-82qdd evicting pod ns-rxzwd/redis-lyqvhu-redis-sentinel-2 evicting pod ns-rxzwd/redis-lyqvhu-redis-twemproxy-2 evicting pod ns-ybzhw/gaussdb-bpsmmq-gaussdb-1 pod/kafka-esbuyt-kafka-producer evicted pod/damengdb-tkwqqh-dmdb-1 evicted pod/kb-addon-prometheus-server-0 evicted pod/chaos-dashboard-7b866cc765-tf2t7 evicted pod/chaos-controller-manager-675887849-f24b7 evicted pod/keda-admission-webhooks-57ffdc99c4-r76s8 evicted pod/damengdb-tkwqqh-dmdb-2 evicted pod/kafka-esbuyt-kafka-exporter-0 evicted pod/kafka-esbuyt-kafka-zookeeper-0 evicted pod/postgres-ywrmpr-postgresql-0 evicted pod/chaos-dns-server-cd7c67cc5-phlmw evicted pod/chaos-controller-manager-675887849-jnxpw evicted pod/kb-addon-grafana-77bd68f6b8-65d59 evicted I0901 12:27:42.290148 16194 request.go:697] Waited for 1.000107354s due to client-side throttling, not priority and fairness, request: POST:https://communal-bream-k8s-xgiego06.hcp.eastus.azmk8s.io:443/api/v1/namespaces/kb-hmwej/pods/kubeblocks-54b68fc4f9-qzsqk/eviction pod/kubeblocks-54b68fc4f9-qzsqk evicted pod/keda-operator-metrics-apiserver-7895dbb47b-6dplq evicted pod/kafka-esbuyt-kafka-broker-1 evicted pod/metrics-server-6b88d9f9c9-sfnzl evicted error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. pod/redis-lyqvhu-redis-0 evicted pod/konnectivity-agent-867755898d-xj98n evicted pod/kafka-esbuyt-kafka-zookeeper-2 evicted pod/redis-lyqvhu-redis-sentinel-2 evicted pod/apemysql-txrgwo-mysql-1 evicted pod/chaos-controller-manager-675887849-l8l56 evicted pod/keda-operator-68b7db459f-82qdd evicted pod/redis-lyqvhu-redis-twemproxy-2 evicted pod/gaussdb-bpsmmq-gaussdb-1 evicted evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 There are pending pods in node "aks-cicdamdpool-38368475-vmss000006" when an error occurred: error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system": global timeout reached: 1m0s pod/metrics-server-6b88d9f9c9-ld894 error: unable to drain node "aks-cicdamdpool-38368475-vmss000006" due to error:error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system": global timeout reached: 1m0s, continuing command... There are pending nodes to be drained: aks-cicdamdpool-38368475-vmss000006 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system": global timeout reached: 1m0s node/aks-cicdamdpool-38368475-vmss000006 already cordoned Warning: ignoring DaemonSet-managed Pods: chaos-mesh/chaos-daemon-vs6fn, kb-hmwej/kb-addon-apecloud-otel-collector-dcrnn, kube-system/azure-cns-lfghc, kube-system/azure-ip-masq-agent-rl2nt, kube-system/cloud-node-manager-vsbz9, kube-system/csi-azuredisk-node-kqwnx, kube-system/csi-azurefile-node-7w5bm, kube-system/kube-proxy-wrvb2 evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 error when evicting pods/"metrics-server-6b88d9f9c9-ld894" -n "kube-system" (will retry after 5s): Cannot evict pod as it would violate the pod's disruption budget. evicting pod kube-system/metrics-server-6b88d9f9c9-ld894 pod/metrics-server-6b88d9f9c9-ld894 evicted node/aks-cicdamdpool-38368475-vmss000006 drained kubectl uncordon aks-cicdamdpool-38368475-vmss000006 node/aks-cicdamdpool-38368475-vmss000006 uncordoned check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 "postgres-ywrmpr-postgresql-0" force deleted cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:31 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 12:25 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover drainnode Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cluster configure component_tmp: postgresql check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster configure postgres-ywrmpr --auto-approve --force=true --set max_connections=200 --components postgresql --config-spec postgresql-configuration --config-file postgresql.conf --namespace ns-yztjr ` Will updated configure file meta: ConfigSpec: postgresql-configuration ConfigFile: postgresql.conf ComponentName: postgresql ClusterName: postgres-ywrmpr OpsRequest postgres-ywrmpr-reconfiguring-fnv5w created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-reconfiguring-fnv5w -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-reconfiguring-fnv5w ns-yztjr Reconfiguring postgres-ywrmpr postgresql Pending -/- Sep 01,2025 12:34 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:31 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 12:25 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-reconfiguring-fnv5w ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 12:34 UTC+0800 check ops status done ops_status:postgres-ywrmpr-postgresql-backup-schedule-wnmp8 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:36 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-nw9sn ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 11:44 UTC+0800 postgres-ywrmpr-reconfiguring-fnv5w ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 12:34 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-postgresql-backup-schedule-wnmp8 --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule-wnmp8 patched `kbcli cluster delete-ops --name postgres-ywrmpr-postgresql-backup-schedule-wnmp8 --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-postgresql-backup-schedule-wnmp8 deleted `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-postgresql-backup-schedule-nw9sn --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule-nw9sn patched `kbcli cluster delete-ops --name postgres-ywrmpr-postgresql-backup-schedule-nw9sn --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-postgresql-backup-schedule-nw9sn deleted `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-reconfiguring-fnv5w --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-reconfiguring-fnv5w patched `kbcli cluster delete-ops --name postgres-ywrmpr-reconfiguring-fnv5w --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-reconfiguring-fnv5w deleted check config variables Unable to use a TTY - input is not a terminal or the right kind of file current value_actual: 200 configure:[max_connections] result actual:[200] equal expected:[200] `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success 12 test failover podkill check cluster status before cluster-failover-podkill check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge PodChaos test-chaos-mesh-podkill-postgres-ywrmpr --namespace ns-yztjr ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podkill-postgres-ywrmpr" not found Error from server (NotFound): podchaos.chaos-mesh.org "test-chaos-mesh-podkill-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: PodChaos metadata: name: test-chaos-mesh-podkill-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-1 mode: all action: pod-kill `kubectl apply -f test-chaos-mesh-podkill-postgres-ywrmpr.yaml` podchaos.chaos-mesh.org/test-chaos-mesh-podkill-postgres-ywrmpr created apply test-chaos-mesh-podkill-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-podkill-postgres-ywrmpr.yaml` check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 "postgres-ywrmpr-postgresql-1" force deleted cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating 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 postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:31 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:36 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge PodChaos test-chaos-mesh-podkill-postgres-ywrmpr --namespace ns-yztjr ` Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. podchaos.chaos-mesh.org "test-chaos-mesh-podkill-postgres-ywrmpr" force deleted podchaos.chaos-mesh.org/test-chaos-mesh-podkill-postgres-ywrmpr patched check failover pod name failover pod name:postgres-ywrmpr-postgresql-0 failover podkill Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cluster configure component_tmp: postgresql check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster configure postgres-ywrmpr --auto-approve --force=true --set shared_buffers=512MB --components postgresql --config-spec postgresql-configuration --config-file postgresql.conf --namespace ns-yztjr ` Will updated configure file meta: ConfigSpec: postgresql-configuration ConfigFile: postgresql.conf ComponentName: postgresql ClusterName: postgres-ywrmpr OpsRequest postgres-ywrmpr-reconfiguring-cf8k2 created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-reconfiguring-cf8k2 -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-reconfiguring-cf8k2 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Pending -/- Sep 01,2025 12:38 UTC+0800 ops_status:postgres-ywrmpr-reconfiguring-cf8k2 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Creating -/- Sep 01,2025 12:38 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:40 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:38 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-reconfiguring-cf8k2 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 12:38 UTC+0800 check ops status done ops_status:postgres-ywrmpr-reconfiguring-cf8k2 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 12:38 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-reconfiguring-cf8k2 --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-reconfiguring-cf8k2 patched `kbcli cluster delete-ops --name postgres-ywrmpr-reconfiguring-cf8k2 --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-reconfiguring-cf8k2 deleted check config variables Unable to use a TTY - input is not a terminal or the right kind of file current value_actual: 512MB configure:[shared_buffers] result actual:[512MB] equal expected:[512MB] `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover timeoffset check cluster status before cluster-failover-timeoffset check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge TimeChaos test-chaos-mesh-timeoffset-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" not found Error from server (NotFound): timechaos.chaos-mesh.org "test-chaos-mesh-timeoffset-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: TimeChaos metadata: name: test-chaos-mesh-timeoffset-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-1 mode: all timeOffset: '-10m' clockIds: - CLOCK_REALTIME duration: 2m `kubectl apply -f test-chaos-mesh-timeoffset-postgres-ywrmpr.yaml` timechaos.chaos-mesh.org/test-chaos-mesh-timeoffset-postgres-ywrmpr created apply test-chaos-mesh-timeoffset-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-timeoffset-postgres-ywrmpr.yaml` timeoffset chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:40 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:38 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge TimeChaos test-chaos-mesh-timeoffset-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" force deleted Error from server (NotFound): timechaos.chaos-mesh.org "test-chaos-mesh-timeoffset-postgres-ywrmpr" not found check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover timeoffset Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover networkbandwidthover check cluster status before cluster-failover-networkbandwidthover check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkbandwidthover-postgres-ywrmpr --namespace ns-yztjr ` 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-networkbandwidthover-postgres-ywrmpr" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkbandwidthover-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkbandwidthover-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-1 action: bandwidth mode: all bandwidth: rate: '1bps' limit: 20971520 buffer: 10000 duration: 2m `kubectl apply -f test-chaos-mesh-networkbandwidthover-postgres-ywrmpr.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkbandwidthover-postgres-ywrmpr created apply test-chaos-mesh-networkbandwidthover-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-networkbandwidthover-postgres-ywrmpr.yaml` networkbandwidthover chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:40 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:38 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkbandwidthover-postgres-ywrmpr --namespace ns-yztjr ` 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-networkbandwidthover-postgres-ywrmpr" force deleted networkchaos.chaos-mesh.org/test-chaos-mesh-networkbandwidthover-postgres-ywrmpr patched check failover pod name failover pod name:postgres-ywrmpr-postgresql-0 failover networkbandwidthover Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover faultover check cluster status before cluster-failover-faultover check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge IOChaos test-chaos-mesh-faultover-postgres-ywrmpr --namespace ns-yztjr ` 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): iochaos.chaos-mesh.org "test-chaos-mesh-faultover-postgres-ywrmpr" not found Error from server (NotFound): iochaos.chaos-mesh.org "test-chaos-mesh-faultover-postgres-ywrmpr" not found LINUX ERRNO: 16: Device or resource busy apiVersion: chaos-mesh.org/v1alpha1 kind: IOChaos metadata: name: test-chaos-mesh-faultover-postgres-ywrmpr namespace: ns-yztjr spec: action: fault mode: all selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-0 volumePath: /home/postgres/pgdata path: '/home/postgres/pgdata/**/*' errno: 16 percent: 100 duration: 2m `kubectl apply -f test-chaos-mesh-faultover-postgres-ywrmpr.yaml` iochaos.chaos-mesh.org/test-chaos-mesh-faultover-postgres-ywrmpr created apply test-chaos-mesh-faultover-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-faultover-postgres-ywrmpr.yaml` faultover chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:40 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:38 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge IOChaos test-chaos-mesh-faultover-postgres-ywrmpr --namespace ns-yztjr ` 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. iochaos.chaos-mesh.org "test-chaos-mesh-faultover-postgres-ywrmpr" force deleted Error from server (NotFound): iochaos.chaos-mesh.org "test-chaos-mesh-faultover-postgres-ywrmpr" not found check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover faultover Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover kill1 check cluster status before cluster-failover-kill1 check cluster status done cluster_status:Running check node drain check node drain success `kill 1` Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (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 postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:40 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:38 UTC+0800 pod_status:Error check pod status done check cluster role No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: No resources found in ns-yztjr namespace. primary: postgres-ywrmpr-postgresql-0 postgres-ywrmpr-postgresql-1;secondary: check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check failover pod name failover pod name:postgres-ywrmpr-postgresql-0 failover kill1 Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover attroverride check cluster status before cluster-failover-attroverride cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge IOChaos test-chaos-mesh-attroverride-postgres-ywrmpr --namespace ns-yztjr ` 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): iochaos.chaos-mesh.org "test-chaos-mesh-attroverride-postgres-ywrmpr" not found Error from server (NotFound): iochaos.chaos-mesh.org "test-chaos-mesh-attroverride-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: IOChaos metadata: name: test-chaos-mesh-attroverride-postgres-ywrmpr namespace: ns-yztjr spec: action: attrOverride mode: all selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-0 volumePath: /home/postgres/pgdata path: '/home/postgres/pgdata/**/*' attr: perm: 72 percent: 100 duration: 2m `kubectl apply -f test-chaos-mesh-attroverride-postgres-ywrmpr.yaml` iochaos.chaos-mesh.org/test-chaos-mesh-attroverride-postgres-ywrmpr created apply test-chaos-mesh-attroverride-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-attroverride-postgres-ywrmpr.yaml` attroverride chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:40 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:38 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge IOChaos test-chaos-mesh-attroverride-postgres-ywrmpr --namespace ns-yztjr ` 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. iochaos.chaos-mesh.org "test-chaos-mesh-attroverride-postgres-ywrmpr" force deleted iochaos.chaos-mesh.org/test-chaos-mesh-attroverride-postgres-ywrmpr patched check failover pod name failover pod name:postgres-ywrmpr-postgresql-0 failover attroverride Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover mistake check cluster status before cluster-failover-mistake check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge IOChaos test-chaos-mesh-mistake-postgres-ywrmpr --namespace ns-yztjr ` 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): iochaos.chaos-mesh.org "test-chaos-mesh-mistake-postgres-ywrmpr" not found Error from server (NotFound): iochaos.chaos-mesh.org "test-chaos-mesh-mistake-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: IOChaos metadata: name: test-chaos-mesh-mistake-postgres-ywrmpr namespace: ns-yztjr spec: action: mistake mode: all selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-0 volumePath: /home/postgres/pgdata path: '/home/postgres/pgdata/**/*' mistake: filling: zero maxOccurrences: 1 maxLength: 10 methods: - READ - WRITE percent: 100 duration: 2m `kubectl apply -f test-chaos-mesh-mistake-postgres-ywrmpr.yaml` iochaos.chaos-mesh.org/test-chaos-mesh-mistake-postgres-ywrmpr created apply test-chaos-mesh-mistake-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-mistake-postgres-ywrmpr.yaml` mistake chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:40 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:38 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge IOChaos test-chaos-mesh-mistake-postgres-ywrmpr --namespace ns-yztjr ` 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. iochaos.chaos-mesh.org "test-chaos-mesh-mistake-postgres-ywrmpr" force deleted iochaos.chaos-mesh.org/test-chaos-mesh-mistake-postgres-ywrmpr patched check failover pod name failover pod name:postgres-ywrmpr-postgresql-0 failover mistake Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cluster hscale check cluster status before ops check cluster status done cluster_status:Running No resources found in postgres-ywrmpr namespace. `kbcli cluster hscale postgres-ywrmpr --auto-approve --force=true --components postgresql --replicas 3 --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-horizontalscaling-rh7wr created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-horizontalscaling-rh7wr -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-horizontalscaling-rh7wr ns-yztjr HorizontalScaling postgres-ywrmpr postgresql Creating -/- Sep 01,2025 12:54 UTC+0800 ops_status:postgres-ywrmpr-horizontalscaling-rh7wr ns-yztjr HorizontalScaling postgres-ywrmpr postgresql Creating -/- Sep 01,2025 12:54 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:40 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:38 UTC+0800 postgres-ywrmpr-postgresql-2 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000000/10.224.0.5 Sep 01,2025 12:54 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 postgres-ywrmpr-postgresql-2 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done No resources found in postgres-ywrmpr namespace. check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-horizontalscaling-rh7wr ns-yztjr HorizontalScaling postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 12:54 UTC+0800 check ops status done ops_status:postgres-ywrmpr-horizontalscaling-rh7wr ns-yztjr HorizontalScaling postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 12:54 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-horizontalscaling-rh7wr --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-horizontalscaling-rh7wr patched `kbcli cluster delete-ops --name postgres-ywrmpr-horizontalscaling-rh7wr --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-horizontalscaling-rh7wr deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary), postgres-ywrmpr-postgresql-2(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cluster hscale check cluster status before ops check cluster status done cluster_status:Running No resources found in postgres-ywrmpr namespace. `kbcli cluster hscale postgres-ywrmpr --auto-approve --force=true --components postgresql --replicas 2 --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-horizontalscaling-82jxp created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-horizontalscaling-82jxp -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-horizontalscaling-82jxp ns-yztjr HorizontalScaling postgres-ywrmpr postgresql Pending -/- Sep 01,2025 12:56 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= 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 postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:40 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:38 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done No resources found in postgres-ywrmpr namespace. check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-horizontalscaling-82jxp ns-yztjr HorizontalScaling postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 12:56 UTC+0800 check ops status done ops_status:postgres-ywrmpr-horizontalscaling-82jxp ns-yztjr HorizontalScaling postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 12:56 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-horizontalscaling-82jxp --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-horizontalscaling-82jxp patched `kbcli cluster delete-ops --name postgres-ywrmpr-horizontalscaling-82jxp --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-horizontalscaling-82jxp deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover networkcorruptover check cluster status before cluster-failover-networkcorruptover check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkcorruptover-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkcorruptover-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkcorruptover-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-0 mode: all action: corrupt corrupt: corrupt: '100' correlation: '100' direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkcorruptover-postgres-ywrmpr.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkcorruptover-postgres-ywrmpr created apply test-chaos-mesh-networkcorruptover-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-networkcorruptover-postgres-ywrmpr.yaml` networkcorruptover chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:40 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:38 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkcorruptover-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" force deleted networkchaos.chaos-mesh.org/test-chaos-mesh-networkcorruptover-postgres-ywrmpr patched check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover networkcorruptover Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover networkpartition check cluster status before cluster-failover-networkpartition check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkpartition-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkpartition-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkpartition-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-1 action: partition mode: all target: mode: all selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-0 direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkpartition-postgres-ywrmpr.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkpartition-postgres-ywrmpr created apply test-chaos-mesh-networkpartition-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-networkpartition-postgres-ywrmpr.yaml` networkpartition chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 12:40 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 12:38 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkpartition-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" force deleted Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkpartition-postgres-ywrmpr" not found check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover networkpartition Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop postgres-ywrmpr --auto-approve --force=true --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-stop-6sr8z created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-stop-6sr8z -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-stop-6sr8z ns-yztjr Stop postgres-ywrmpr Pending -/- Sep 01,2025 13:01 UTC+0800 ops_status:postgres-ywrmpr-stop-6sr8z ns-yztjr Stop postgres-ywrmpr Creating -/- Sep 01,2025 13:01 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Stopping Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping cluster_status:Stopping check cluster status done cluster_status:Stopped check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` 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 postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-stop-6sr8z ns-yztjr Stop postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 13:01 UTC+0800 check ops status done ops_status:postgres-ywrmpr-stop-6sr8z ns-yztjr Stop postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 13:01 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-stop-6sr8z --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-stop-6sr8z patched `kbcli cluster delete-ops --name postgres-ywrmpr-stop-6sr8z --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-stop-6sr8z deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start postgres-ywrmpr --force=true --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-start-jwm5c created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-start-jwm5c -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-start-jwm5c ns-yztjr Start postgres-ywrmpr Creating -/- Sep 01,2025 13:02 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= 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 postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:02 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:02 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-start-jwm5c ns-yztjr Start postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 13:02 UTC+0800 check ops status done ops_status:postgres-ywrmpr-start-jwm5c ns-yztjr Start postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 13:02 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-start-jwm5c --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-start-jwm5c patched `kbcli cluster delete-ops --name postgres-ywrmpr-start-jwm5c --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-start-jwm5c deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover oom check cluster status before cluster-failover-oom check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-oom-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" not found Error from server (NotFound): stresschaos.chaos-mesh.org "test-chaos-mesh-oom-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: StressChaos metadata: name: test-chaos-mesh-oom-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-0 mode: all stressors: memory: workers: 1 size: "100GB" oomScoreAdj: -1000 duration: 2m `kubectl apply -f test-chaos-mesh-oom-postgres-ywrmpr.yaml` stresschaos.chaos-mesh.org/test-chaos-mesh-oom-postgres-ywrmpr created apply test-chaos-mesh-oom-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-oom-postgres-ywrmpr.yaml` check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:02 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:02 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge StressChaos test-chaos-mesh-oom-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" force deleted stresschaos.chaos-mesh.org/test-chaos-mesh-oom-postgres-ywrmpr patched check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover oom Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test failover connectionstress check cluster status before cluster-failover-connectionstress check cluster status done cluster_status:Running check node drain check node drain success Error from server (NotFound): pods "test-db-client-connectionstress-postgres-ywrmpr" not found `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-connectionstress-postgres-ywrmpr --namespace ns-yztjr ` Error from server (NotFound): pods "test-db-client-connectionstress-postgres-ywrmpr" not found Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. Error from server (NotFound): pods "test-db-client-connectionstress-postgres-ywrmpr" not found `kubectl get secrets -l app.kubernetes.io/instance=postgres-ywrmpr` set secret: postgres-ywrmpr-postgresql-account-postgres `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.username***"` `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.password***"` `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.port***"` DB_USERNAME:postgres;DB_PASSWORD:8sv2A053Oz;DB_PORT:5432;DB_DATABASE:postgres apiVersion: v1 kind: Pod metadata: name: test-db-client-connectionstress-postgres-ywrmpr namespace: ns-yztjr spec: containers: - name: test-dbclient imagePullPolicy: IfNotPresent image: docker.io/apecloud/dbclient:test args: - "--host" - "postgres-ywrmpr-postgresql-postgresql.ns-yztjr.svc.cluster.local" - "--user" - "postgres" - "--password" - "8sv2A053Oz" - "--port" - "5432" - "--database" - "postgres" - "--dbtype" - "postgresql" - "--test" - "connectionstress" - "--connections" - "56" - "--duration" - "60" restartPolicy: Never `kubectl apply -f test-db-client-connectionstress-postgres-ywrmpr.yaml` pod/test-db-client-connectionstress-postgres-ywrmpr created apply test-db-client-connectionstress-postgres-ywrmpr.yaml Success `rm -rf test-db-client-connectionstress-postgres-ywrmpr.yaml` check pod status check pod test-db-client-connectionstress-postgres-ywrmpr status done pod_status:NAME READY STATUS RESTARTS AGE test-db-client-connectionstress-postgres-ywrmpr 0/1 Completed 0 6s check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:02 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:02 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done --host postgres-ywrmpr-postgresql-postgresql.ns-yztjr.svc.cluster.local --user postgres --password 8sv2A053Oz --port 5432 --database postgres --dbtype postgresql --test connectionstress --connections 56 --duration 60 SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider] WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.postgresql.jdbc.TimestampUtils (file:/app/oneclient-1.0-all.jar) to field java.util.TimeZone.defaultTimeZone WARNING: Please consider reporting this to the maintainers of org.postgresql.jdbc.TimestampUtils WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Test Result: null Connection Information: Database Type: postgresql Host: postgres-ywrmpr-postgresql-postgresql.ns-yztjr.svc.cluster.local Port: 5432 Database: postgres Table: User: postgres Org: Access Mode: mysql Test Type: connectionstress Connection Count: 56 Duration: 60 seconds `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge pods test-db-client-connectionstress-postgres-ywrmpr --namespace ns-yztjr ` pod/test-db-client-connectionstress-postgres-ywrmpr patched (no change) Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely. pod "test-db-client-connectionstress-postgres-ywrmpr" force deleted check failover pod name failover pod name:postgres-ywrmpr-postgresql-1 failover connectionstress Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cluster update enable-all-logs `kbcli cluster update postgres-ywrmpr --enable-all-logs=true --namespace ns-yztjr ` error: failed to reconfigure log variables of target cluster: no config templates for component postgresql check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:02 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:02 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done test failover networkdelay check cluster status before cluster-failover-networkdelay check cluster status done cluster_status:Running check node drain check node drain success `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkdelay-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr" not found Error from server (NotFound): networkchaos.chaos-mesh.org "test-chaos-mesh-networkdelay-postgres-ywrmpr" not found apiVersion: chaos-mesh.org/v1alpha1 kind: NetworkChaos metadata: name: test-chaos-mesh-networkdelay-postgres-ywrmpr namespace: ns-yztjr spec: selector: namespaces: - ns-yztjr labelSelectors: apps.kubeblocks.io/pod-name: postgres-ywrmpr-postgresql-1 mode: all action: delay delay: latency: 2000ms correlation: '100' jitter: 0ms direction: to duration: 2m `kubectl apply -f test-chaos-mesh-networkdelay-postgres-ywrmpr.yaml` networkchaos.chaos-mesh.org/test-chaos-mesh-networkdelay-postgres-ywrmpr created apply test-chaos-mesh-networkdelay-postgres-ywrmpr.yaml Success `rm -rf test-chaos-mesh-networkdelay-postgres-ywrmpr.yaml` networkdelay chaos test waiting 120 seconds check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:02 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:3Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:02 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge NetworkChaos test-chaos-mesh-networkdelay-postgres-ywrmpr --namespace ns-yztjr ` 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-postgres-ywrmpr patched check failover pod name networkchaos.chaos-mesh.org "test-chaos-mesh-networkdelay-postgres-ywrmpr" force deleted failover pod name:postgres-ywrmpr-postgresql-1 failover networkdelay Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success `kubectl get pvc -l app.kubernetes.io/instance=postgres-ywrmpr,apps.kubeblocks.io/component-name=postgresql,apps.kubeblocks.io/vct-name=data --namespace ns-yztjr ` cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in postgres-ywrmpr namespace. `kbcli cluster volume-expand postgres-ywrmpr --auto-approve --force=true --components postgresql --volume-claim-templates data --storage 4Gi --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-volumeexpansion-hkzd4 created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-volumeexpansion-hkzd4 -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-volumeexpansion-hkzd4 ns-yztjr VolumeExpansion postgres-ywrmpr postgresql Creating -/- Sep 01,2025 13:08 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Updating Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating cluster_status:Updating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:02 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:02 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-1;secondary: postgres-ywrmpr-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done No resources found in postgres-ywrmpr namespace. check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-volumeexpansion-hkzd4 ns-yztjr VolumeExpansion postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 13:08 UTC+0800 check ops status done ops_status:postgres-ywrmpr-volumeexpansion-hkzd4 ns-yztjr VolumeExpansion postgres-ywrmpr postgresql Succeed 2/2 Sep 01,2025 13:08 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-volumeexpansion-hkzd4 --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-volumeexpansion-hkzd4 patched `kbcli cluster delete-ops --name postgres-ywrmpr-volumeexpansion-hkzd4 --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-volumeexpansion-hkzd4 deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-1: out of postgres-ywrmpr-postgresql-1(primary), postgres-ywrmpr-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-0 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success test switchover cluster promote check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster promote postgres-ywrmpr --auto-approve --force=true --component postgresql --namespace ns-yztjr ` component:postgresql OpsRequest postgres-ywrmpr-switchover-c76mr created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-switchover-c76mr -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-switchover-c76mr ns-yztjr Switchover postgres-ywrmpr postgresql Creating -/- Sep 01,2025 13:14 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:02 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:02 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-switchover-c76mr ns-yztjr Switchover postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 13:14 UTC+0800 check ops status done ops_status:postgres-ywrmpr-switchover-c76mr ns-yztjr Switchover postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 13:14 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-switchover-c76mr --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-switchover-c76mr patched `kbcli cluster delete-ops --name postgres-ywrmpr-switchover-c76mr --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-switchover-c76mr deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success switchover pod:postgres-ywrmpr-postgresql-0 switchover success `kubectl get secrets -l app.kubernetes.io/instance=postgres-ywrmpr` set secret: postgres-ywrmpr-postgresql-account-postgres `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.username***"` `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.password***"` `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.port***"` DB_USERNAME:postgres;DB_PASSWORD:8sv2A053Oz;DB_PORT:5432;DB_DATABASE:postgres `create database benchtest;` 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:Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) DROP DATABASE CREATE DATABASE apiVersion: v1 kind: Pod metadata: name: benchtest-postgres-ywrmpr namespace: ns-yztjr 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:postgres-ywrmpr-postgresql-postgresql.ns-yztjr.svc.cluster.local,user:postgres,password:8sv2A053Oz,port:5432,db:benchtest,tables:5,threads:4,times:10,size:1000,type:oltp_read_write" restartPolicy: Never `kubectl apply -f benchtest-postgres-ywrmpr.yaml` pod/benchtest-postgres-ywrmpr created apply benchtest-postgres-ywrmpr.yaml Success check pod status pod_status:NAME READY STATUS RESTARTS AGE benchtest-postgres-ywrmpr 0/1 ContainerCreating 0 0s pod_status:NAME READY STATUS RESTARTS AGE benchtest-postgres-ywrmpr 1/1 Running 0 4s pod_status:NAME READY STATUS RESTARTS AGE benchtest-postgres-ywrmpr 1/1 Running 0 9s check pod benchtest-postgres-ywrmpr status done pod_status:NAME READY STATUS RESTARTS AGE benchtest-postgres-ywrmpr 0/1 Completed 0 14s `rm -rf benchtest-postgres-ywrmpr.yaml` `kubectl logs benchtest-postgres-ywrmpr --tail 30 --namespace ns-yztjr ` [ 7s ] thds: 4 tps: 62.98 qps: 1262.65 (r/w/o: 879.75/252.93/129.96) lat (ms,99%): 99.33 err/s: 1.00 reconn/s: 0.00 [ 8s ] thds: 4 tps: 57.00 qps: 1173.09 (r/w/o: 829.06/230.02/114.01) lat (ms,99%): 99.33 err/s: 0.00 reconn/s: 0.00 [ 9s ] thds: 4 tps: 57.01 qps: 1156.20 (r/w/o: 808.14/231.04/117.02) lat (ms,99%): 193.38 err/s: 1.00 reconn/s: 0.00 [ 10s ] thds: 4 tps: 65.99 qps: 1320.77 (r/w/o: 926.84/261.95/131.98) lat (ms,99%): 99.33 err/s: 0.00 reconn/s: 0.00 SQL statistics: queries performed: read: 7896 write: 2234 other: 1136 total: 11266 transactions: 557 (55.14 per sec.) queries: 11266 (1115.34 per sec.) ignored errors: 7 (0.69 per sec.) reconnects: 0 (0.00 per sec.) General statistics: total time: 10.0994s total number of events: 557 Latency (ms): min: 4.73 avg: 72.49 max: 198.00 99th percentile: 193.38 sum: 40377.46 Threads fairness: events (avg/stddev): 139.2500/3.42 execution time (avg/stddev): 10.0944/0.00 `kubectl delete pod benchtest-postgres-ywrmpr --force --namespace ns-yztjr ` 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-postgres-ywrmpr" force deleted No resources found in ns-yztjr namespace. `kubectl get secrets -l app.kubernetes.io/instance=postgres-ywrmpr` set secret: postgres-ywrmpr-postgresql-account-postgres `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.username***"` `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.password***"` `kubectl get secrets postgres-ywrmpr-postgresql-account-postgres -o jsonpath="***.data.port***"` DB_USERNAME:postgres;DB_PASSWORD:8sv2A053Oz;DB_PORT:5432;DB_DATABASE:postgres `create database benchtest;` Unable to use a TTY - input is not a terminal or the right kind of file return msg:Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) DROP DATABASE CREATE DATABASE apiVersion: v1 kind: Pod metadata: name: benchtest-postgres-ywrmpr namespace: ns-yztjr 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.6,user:postgres,password:8sv2A053Oz,port:5432,db:benchtest,tables:5,threads:4,times:10,size:1000,type:oltp_read_write" restartPolicy: Never `kubectl apply -f benchtest-postgres-ywrmpr.yaml` pod/benchtest-postgres-ywrmpr created apply benchtest-postgres-ywrmpr.yaml Success check pod status pod_status:NAME READY STATUS RESTARTS AGE benchtest-postgres-ywrmpr 0/1 ContainerCreating 0 0s pod_status:NAME READY STATUS RESTARTS AGE benchtest-postgres-ywrmpr 1/1 Running 0 5s pod_status:NAME READY STATUS RESTARTS AGE benchtest-postgres-ywrmpr 1/1 Running 0 10s pod_status:NAME READY STATUS RESTARTS AGE benchtest-postgres-ywrmpr 1/1 Running 0 15s check pod benchtest-postgres-ywrmpr status done pod_status:NAME READY STATUS RESTARTS AGE benchtest-postgres-ywrmpr 0/1 Completed 0 20s `rm -rf benchtest-postgres-ywrmpr.yaml` `kubectl logs benchtest-postgres-ywrmpr --tail 30 --namespace ns-yztjr ` [ 7s ] thds: 4 tps: 55.99 qps: 1118.89 (r/w/o: 789.93/215.98/112.99) lat (ms,99%): 99.33 err/s: 0.00 reconn/s: 0.00 [ 8s ] thds: 4 tps: 60.00 qps: 1205.09 (r/w/o: 846.06/237.02/122.01) lat (ms,99%): 99.33 err/s: 0.00 reconn/s: 0.00 [ 9s ] thds: 4 tps: 65.99 qps: 1351.80 (r/w/o: 947.86/265.96/137.98) lat (ms,99%): 101.13 err/s: 2.00 reconn/s: 0.00 [ 10s ] thds: 4 tps: 58.00 qps: 1221.04 (r/w/o: 855.03/241.01/125.00) lat (ms,99%): 104.84 err/s: 4.00 reconn/s: 0.00 SQL statistics: queries performed: read: 7840 write: 2205 other: 1135 total: 11180 transactions: 550 (54.46 per sec.) queries: 11180 (1107.06 per sec.) ignored errors: 10 (0.99 per sec.) reconnects: 0 (0.00 per sec.) General statistics: total time: 10.0972s total number of events: 550 Latency (ms): min: 4.48 avg: 73.41 max: 200.57 99th percentile: 196.89 sum: 40373.96 Threads fairness: events (avg/stddev): 137.5000/3.64 execution time (avg/stddev): 10.0935/0.00 `kubectl delete pod benchtest-postgres-ywrmpr --force --namespace ns-yztjr ` 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-postgres-ywrmpr" force deleted cluster update terminationPolicy WipeOut `kbcli cluster update postgres-ywrmpr --termination-policy=WipeOut --namespace ns-yztjr ` cluster.apps.kubeblocks.io/postgres-ywrmpr updated (no change) check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:02 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:02 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done cluster pg-basebackup backup `kubectl get backuprepo backuprepo-kbcli-test -o jsonpath="***.spec.credential.name***"` `kubectl get backuprepo backuprepo-kbcli-test -o jsonpath="***.spec.credential.namespace***"` `kubectl get secrets kb-backuprepo-bxwnt -n kb-hmwej -o jsonpath="***.data.accessKeyId***"` `kubectl get secrets kb-backuprepo-bxwnt -n kb-hmwej -o jsonpath="***.data.secretAccessKey***"` KUBEBLOCKS NAMESPACE:kb-hmwej get kubeblocks namespace done `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-hmwej -o jsonpath="***.items[0].data.root-user***"` `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-hmwej -o jsonpath="***.items[0].data.root-password***"` minio_user:kbclitest,minio_password:kbclitest,minio_endpoint:kbcli-test-minio.kb-hmwej.svc.cluster.local:9000 list minio bucket kbcli-test `echo 'mc config host add minioserver http://kbcli-test-minio.kb-hmwej.svc.cluster.local:9000 kbclitest kbclitest;mc ls minioserver' | kubectl exec -it kbcli-test-minio-669d87677b-7sjlg --namespace kb-hmwej -- bash` Unable to use a TTY - input is not a terminal or the right kind of file list minio bucket done default backuprepo:backuprepo-kbcli-test exists `kbcli cluster backup postgres-ywrmpr --method pg-basebackup --namespace ns-yztjr ` Backup backup-ns-yztjr-postgres-ywrmpr-20250901131744 created successfully, you can view the progress: kbcli cluster list-backups --name=backup-ns-yztjr-postgres-ywrmpr-20250901131744 -n ns-yztjr check backup status `kbcli cluster list-backups postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE SOURCE-CLUSTER METHOD STATUS TOTAL-SIZE DURATION CREATE-TIME COMPLETION-TIME EXPIRATION backup-ns-yztjr-postgres-ywrmpr-20250901131744 ns-yztjr postgres-ywrmpr pg-basebackup Sep 01,2025 13:17 UTC+0800 backup_status:postgres-ywrmpr-pg-basebackup-Running backup_status:postgres-ywrmpr-pg-basebackup-Running backup_status:postgres-ywrmpr-pg-basebackup-Running check backup status done backup_status:backup-ns-yztjr-postgres-ywrmpr-20250901131744 ns-yztjr postgres-ywrmpr pg-basebackup Completed 12433514 10s Sep 01,2025 13:17 UTC+0800 Sep 01,2025 13:17 UTC+0800 cluster restore backup Error from server (NotFound): opsrequests.apps.kubeblocks.io "postgres-ywrmpr-backup" not found `kbcli cluster describe-backup backup-ns-yztjr-postgres-ywrmpr-20250901131744 --namespace ns-yztjr ` Name: backup-ns-yztjr-postgres-ywrmpr-20250901131744 Cluster: postgres-ywrmpr Namespace: ns-yztjr Spec: Method: pg-basebackup Policy Name: postgres-ywrmpr-postgresql-backup-policy Status: Phase: Completed Total Size: 12433514 ActionSet Name: postgres-basebackup Repository: backuprepo-kbcli-test Duration: 10s Start Time: Sep 01,2025 13:17 UTC+0800 Completion Time: Sep 01,2025 13:17 UTC+0800 Path: /ns-yztjr/postgres-ywrmpr-49aa172b-1a2e-4216-85cb-d1af9ac7e91b/postgresql/backup-ns-yztjr-postgres-ywrmpr-20250901131744 Time Range Start: Sep 01,2025 13:17 UTC+0800 Time Range End: Sep 01,2025 13:17 UTC+0800 Warning Events: `kbcli cluster restore postgres-ywrmpr-backup --backup backup-ns-yztjr-postgres-ywrmpr-20250901131744 --namespace ns-yztjr ` Cluster postgres-ywrmpr-backup created check cluster status `kbcli cluster list postgres-ywrmpr-backup --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr-backup ns-yztjr postgresql WipeOut Sep 01,2025 13:17 UTC+0800 clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status: cluster_status: cluster_status: cluster_status: cluster_status: cluster_status: cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status: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 postgres-ywrmpr-backup --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-backup-postgresql-0 ns-yztjr postgres-ywrmpr-backup postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:18 UTC+0800 postgres-ywrmpr-backup-postgresql-1 ns-yztjr postgres-ywrmpr-backup postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:18 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-backup-postgresql-1;secondary: postgres-ywrmpr-backup-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr` check cluster connect done `kbcli cluster describe-backup backup-ns-yztjr-postgres-ywrmpr-20250901131744 --namespace ns-yztjr ` Name: backup-ns-yztjr-postgres-ywrmpr-20250901131744 Cluster: postgres-ywrmpr Namespace: ns-yztjr Spec: Method: pg-basebackup Policy Name: postgres-ywrmpr-postgresql-backup-policy Status: Phase: Completed Total Size: 12433514 ActionSet Name: postgres-basebackup Repository: backuprepo-kbcli-test Duration: 10s Start Time: Sep 01,2025 13:17 UTC+0800 Completion Time: Sep 01,2025 13:17 UTC+0800 Path: /ns-yztjr/postgres-ywrmpr-49aa172b-1a2e-4216-85cb-d1af9ac7e91b/postgresql/backup-ns-yztjr-postgres-ywrmpr-20250901131744 Time Range Start: Sep 01,2025 13:17 UTC+0800 Time Range End: Sep 01,2025 13:17 UTC+0800 Warning Events: cluster connect `echo 'create extension vector;' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr --namespace ns-yztjr ` Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file ERROR: extension "vector" already exists Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file List of installed extensions Name | Version | Schema | Description --------------------+---------+------------+----------------------------------------------------------- file_fdw | 1.0 | public | foreign-data wrapper for flat file access pg_auth_mon | 1.1 | public | monitor connection attempts per user pg_cron | 1.6 | pg_catalog | Job scheduler for PostgreSQL pg_stat_kcache | 2.2.3 | public | Kernel statistics gathering pg_stat_statements | 1.7 | public | track execution statistics of all SQL statements executed plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language plpython3u | 1.0 | pg_catalog | PL/Python3U untrusted procedural language set_user | 4.1.0 | public | similar to SET ROLE but with added logging vector | 0.6.1 | public | vector data type and ivfflat and hnsw access methods (9 rows) `echo 'show max_connections;' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr ` Unable to use a TTY - input is not a terminal or the right kind of file Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) max_connections ----------------- 200 (1 row) connect cluster Success set max_connections to 200 delete cluster postgres-ywrmpr-backup `kbcli cluster delete postgres-ywrmpr-backup --auto-approve --namespace ns-yztjr ` Cluster postgres-ywrmpr-backup deleted pod_info:postgres-ywrmpr-backup-postgresql-0 5/5 Running 0 93s postgres-ywrmpr-backup-postgresql-1 5/5 Running 0 93s pod_info:postgres-ywrmpr-backup-postgresql-0 4/5 Terminating 0 113s postgres-ywrmpr-backup-postgresql-1 4/5 Terminating 0 113s No resources found in ns-yztjr namespace. delete cluster pod done No resources found in ns-yztjr namespace. check cluster resource non-exist OK: pvc No resources found in ns-yztjr namespace. delete cluster done No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. cluster rebulid instances apiVersion: apps.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: generateName: postgres-ywrmpr-rebuildinstance- namespace: ns-yztjr spec: type: RebuildInstance clusterName: postgres-ywrmpr force: true rebuildFrom: - componentName: postgresql instances: - name: postgres-ywrmpr-postgresql-1 backupName: backup-ns-yztjr-postgres-ywrmpr-20250901131744 inPlace: false check cluster status before ops check cluster status done cluster_status:Running `kubectl create -f test_ops_cluster_postgres-ywrmpr.yaml` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-rebuildinstance-p8drt created create test_ops_cluster_postgres-ywrmpr.yaml Success `rm -rf test_ops_cluster_postgres-ywrmpr.yaml` check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` No opsrequests found in ns-yztjr namespace. No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: No opsrequests found in ns-yztjr namespace. ops_status: not found ops rebuildinstance check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:02 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:02 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success cluster delete backup `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge backups backup-ns-yztjr-postgres-ywrmpr-20250901131744 --namespace ns-yztjr ` backup.dataprotection.kubeblocks.io/backup-ns-yztjr-postgres-ywrmpr-20250901131744 patched `kbcli cluster delete-backup postgres-ywrmpr --name backup-ns-yztjr-postgres-ywrmpr-20250901131744 --force --auto-approve --namespace ns-yztjr ` Backup backup-ns-yztjr-postgres-ywrmpr-20250901131744 deleted No opsrequests found in ns-yztjr namespace. `kubectl get backupschedule -l app.kubernetes.io/instance=postgres-ywrmpr ` `kubectl get backupschedule postgres-ywrmpr-postgresql-backup-schedule -ojsonpath='***.spec.schedules[*].backupMethod***' ` backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched check backup status `kbcli cluster list-backups postgres-ywrmpr --namespace ns-yztjr ` No backups found in ns-yztjr namespace. No backups found in ns-yztjr namespace. backup_status:-- No backups found in ns-yztjr namespace. backup_status:-- No backups found in ns-yztjr namespace. backup_status:-- No backups found in ns-yztjr namespace. backup_status:-- No backups found in ns-yztjr namespace. backup_status:-- No backups found in ns-yztjr namespace. backup_status:-- No backups found in ns-yztjr namespace. backup_status:-- No backups found in ns-yztjr namespace. backup_status:-- No backups found in ns-yztjr namespace. backup_status:-- No backups found in ns-yztjr namespace. backup_status:-- No backups found in ns-yztjr namespace. backup_status:-- `kubectl get backupschedule -l app.kubernetes.io/instance=postgres-ywrmpr ` `kubectl get backupschedule postgres-ywrmpr-postgresql-backup-schedule -ojsonpath='***.spec.schedules[*].backupMethod***' ` backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backup_status:postgres-ywrmpr-pg-basebackup-Running check backup status done backup_status:postgres-ywrmpr-pg-basebackup-20250901052500 ns-yztjr postgres-ywrmpr pg-basebackup Completed 12433520 11s Sep 01,2025 13:25 UTC+0800 Sep 01,2025 13:25 UTC+0800 Sep 08,2025 13:25 UTC+0800 `kubectl get backupschedule -l app.kubernetes.io/instance=postgres-ywrmpr ` `kubectl get backupschedule postgres-ywrmpr-postgresql-backup-schedule -ojsonpath='***.spec.schedules[*].backupMethod***' ` backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) cluster restore backup Error from server (NotFound): opsrequests.apps.kubeblocks.io "postgres-ywrmpr-backup" not found `kbcli cluster describe-backup postgres-ywrmpr-pg-basebackup-20250901052500 --namespace ns-yztjr ` Name: postgres-ywrmpr-pg-basebackup-20250901052500 Cluster: postgres-ywrmpr Namespace: ns-yztjr Spec: Method: pg-basebackup Policy Name: postgres-ywrmpr-postgresql-backup-policy Status: Phase: Completed Total Size: 12433520 ActionSet Name: postgres-basebackup Repository: backuprepo-kbcli-test Duration: 11s Expiration Time: Sep 08,2025 13:25 UTC+0800 Start Time: Sep 01,2025 13:25 UTC+0800 Completion Time: Sep 01,2025 13:25 UTC+0800 Path: /ns-yztjr/postgres-ywrmpr-49aa172b-1a2e-4216-85cb-d1af9ac7e91b/postgresql/postgres-ywrmpr-pg-basebackup-20250901052500 Time Range Start: Sep 01,2025 13:25 UTC+0800 Time Range End: Sep 01,2025 13:25 UTC+0800 Warning Events: `kbcli cluster restore postgres-ywrmpr-backup --backup postgres-ywrmpr-pg-basebackup-20250901052500 --namespace ns-yztjr ` Cluster postgres-ywrmpr-backup created check cluster status `kbcli cluster list postgres-ywrmpr-backup --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr-backup ns-yztjr postgresql WipeOut Sep 01,2025 13:25 UTC+0800 clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= cluster_status: cluster_status: cluster_status: cluster_status: cluster_status: cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status: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 postgres-ywrmpr-backup --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-backup-postgresql-0 ns-yztjr postgres-ywrmpr-backup postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:25 UTC+0800 postgres-ywrmpr-backup-postgresql-1 ns-yztjr postgres-ywrmpr-backup postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:25 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-backup-postgresql-1;secondary: postgres-ywrmpr-backup-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr` check cluster connect done `kbcli cluster describe-backup postgres-ywrmpr-pg-basebackup-20250901052500 --namespace ns-yztjr ` Name: postgres-ywrmpr-pg-basebackup-20250901052500 Cluster: postgres-ywrmpr Namespace: ns-yztjr Spec: Method: pg-basebackup Policy Name: postgres-ywrmpr-postgresql-backup-policy Status: Phase: Completed Total Size: 12433520 ActionSet Name: postgres-basebackup Repository: backuprepo-kbcli-test Duration: 11s Expiration Time: Sep 08,2025 13:25 UTC+0800 Start Time: Sep 01,2025 13:25 UTC+0800 Completion Time: Sep 01,2025 13:25 UTC+0800 Path: /ns-yztjr/postgres-ywrmpr-49aa172b-1a2e-4216-85cb-d1af9ac7e91b/postgresql/postgres-ywrmpr-pg-basebackup-20250901052500 Time Range Start: Sep 01,2025 13:25 UTC+0800 Time Range End: Sep 01,2025 13:25 UTC+0800 Warning Events: cluster connect `echo 'create extension vector;' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr --namespace ns-yztjr ` Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file ERROR: extension "vector" already exists Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file List of installed extensions Name | Version | Schema | Description --------------------+---------+------------+----------------------------------------------------------- file_fdw | 1.0 | public | foreign-data wrapper for flat file access pg_auth_mon | 1.1 | public | monitor connection attempts per user pg_cron | 1.6 | pg_catalog | Job scheduler for PostgreSQL pg_stat_kcache | 2.2.3 | public | Kernel statistics gathering pg_stat_statements | 1.7 | public | track execution statistics of all SQL statements executed plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language plpython3u | 1.0 | pg_catalog | PL/Python3U untrusted procedural language set_user | 4.1.0 | public | similar to SET ROLE but with added logging vector | 0.6.1 | public | vector data type and ivfflat and hnsw access methods (9 rows) `echo 'show max_connections;' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr ` Unable to use a TTY - input is not a terminal or the right kind of file Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) max_connections ----------------- 200 (1 row) connect cluster Success set max_connections to 200 delete cluster postgres-ywrmpr-backup `kbcli cluster delete postgres-ywrmpr-backup --auto-approve --namespace ns-yztjr ` Cluster postgres-ywrmpr-backup deleted pod_info:postgres-ywrmpr-backup-postgresql-0 5/5 Running 0 83s postgres-ywrmpr-backup-postgresql-1 5/5 Running 0 83s pod_info:postgres-ywrmpr-backup-postgresql-0 4/5 Terminating 0 103s postgres-ywrmpr-backup-postgresql-1 4/5 Terminating 0 103s No resources found in ns-yztjr namespace. delete cluster pod done No resources found in ns-yztjr namespace. check cluster resource non-exist OK: pvc No resources found in ns-yztjr namespace. delete cluster done No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. cluster delete backup `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge backups postgres-ywrmpr-pg-basebackup-20250901052500 --namespace ns-yztjr ` backup.dataprotection.kubeblocks.io/postgres-ywrmpr-pg-basebackup-20250901052500 patched `kbcli cluster delete-backup postgres-ywrmpr --name postgres-ywrmpr-pg-basebackup-20250901052500 --force --auto-approve --namespace ns-yztjr ` Backup postgres-ywrmpr-pg-basebackup-20250901052500 deleted No opsrequests found in ns-yztjr namespace. check cluster storage class cluster volume-snapshot backup `kbcli cluster backup postgres-ywrmpr --method volume-snapshot --namespace ns-yztjr ` Backup backup-ns-yztjr-postgres-ywrmpr-20250901132750 created successfully, you can view the progress: kbcli cluster list-backups --name=backup-ns-yztjr-postgres-ywrmpr-20250901132750 -n ns-yztjr check backup status `kbcli cluster list-backups postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE SOURCE-CLUSTER METHOD STATUS TOTAL-SIZE DURATION CREATE-TIME COMPLETION-TIME EXPIRATION backup-ns-yztjr-postgres-ywrmpr-20250901132750 ns-yztjr postgres-ywrmpr volume-snapshot Sep 01,2025 13:27 UTC+0800 backup_status:postgres-ywrmpr-volume-snapshot-Running backup_status:postgres-ywrmpr-volume-snapshot-Running backup_status:postgres-ywrmpr-volume-snapshot-Running check backup status done backup_status:backup-ns-yztjr-postgres-ywrmpr-20250901132750 ns-yztjr postgres-ywrmpr volume-snapshot Completed 4Gi 14s Sep 01,2025 13:27 UTC+0800 Sep 01,2025 13:28 UTC+0800 cluster restore backup Error from server (NotFound): opsrequests.apps.kubeblocks.io "postgres-ywrmpr-backup" not found `kbcli cluster describe-backup backup-ns-yztjr-postgres-ywrmpr-20250901132750 --namespace ns-yztjr ` Name: backup-ns-yztjr-postgres-ywrmpr-20250901132750 Cluster: postgres-ywrmpr Namespace: ns-yztjr Spec: Method: volume-snapshot Policy Name: postgres-ywrmpr-postgresql-backup-policy Status: Phase: Completed Total Size: 4Gi Duration: 14s Start Time: Sep 01,2025 13:27 UTC+0800 Completion Time: Sep 01,2025 13:28 UTC+0800 Time Range Start: Sep 01,2025 13:27 UTC+0800 Time Range End: Sep 01,2025 13:27 UTC+0800 Warning Events: `kbcli cluster restore postgres-ywrmpr-backup --backup backup-ns-yztjr-postgres-ywrmpr-20250901132750 --namespace ns-yztjr ` Cluster postgres-ywrmpr-backup created check cluster status `kbcli cluster list postgres-ywrmpr-backup --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr-backup ns-yztjr postgresql WipeOut Sep 01,2025 13:28 UTC+0800 cluster_status: cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status:Creating cluster_status: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 postgres-ywrmpr-backup --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-backup-postgresql-0 ns-yztjr postgres-ywrmpr-backup postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:28 UTC+0800 postgres-ywrmpr-backup-postgresql-1 ns-yztjr postgres-ywrmpr-backup postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:28 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-backup-postgresql-1;secondary: postgres-ywrmpr-backup-postgresql-0 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr` check cluster connect done `kbcli cluster describe-backup backup-ns-yztjr-postgres-ywrmpr-20250901132750 --namespace ns-yztjr ` Name: backup-ns-yztjr-postgres-ywrmpr-20250901132750 Cluster: postgres-ywrmpr Namespace: ns-yztjr Spec: Method: volume-snapshot Policy Name: postgres-ywrmpr-postgresql-backup-policy Status: Phase: Completed Total Size: 4Gi Duration: 14s Start Time: Sep 01,2025 13:27 UTC+0800 Completion Time: Sep 01,2025 13:28 UTC+0800 Time Range Start: Sep 01,2025 13:27 UTC+0800 Time Range End: Sep 01,2025 13:27 UTC+0800 Warning Events: cluster connect `echo 'create extension vector;' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr --namespace ns-yztjr ` Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file ERROR: extension "vector" already exists Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) Unable to use a TTY - input is not a terminal or the right kind of file List of installed extensions Name | Version | Schema | Description --------------------+---------+------------+----------------------------------------------------------- file_fdw | 1.0 | public | foreign-data wrapper for flat file access pg_auth_mon | 1.1 | public | monitor connection attempts per user pg_cron | 1.6 | pg_catalog | Job scheduler for PostgreSQL pg_stat_kcache | 2.2.3 | public | Kernel statistics gathering pg_stat_statements | 1.7 | public | track execution statistics of all SQL statements executed plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language plpython3u | 1.0 | pg_catalog | PL/Python3U untrusted procedural language set_user | 4.1.0 | public | similar to SET ROLE but with added logging vector | 0.6.1 | public | vector data type and ivfflat and hnsw access methods (9 rows) `echo 'show max_connections;' | kbcli cluster connect postgres-ywrmpr-backup --namespace ns-yztjr ` Unable to use a TTY - input is not a terminal or the right kind of file Connect to instance postgres-ywrmpr-backup-postgresql-1: out of postgres-ywrmpr-backup-postgresql-1(primary), postgres-ywrmpr-backup-postgresql-0(secondary) max_connections ----------------- 200 (1 row) connect cluster Success set max_connections to 200 delete cluster postgres-ywrmpr-backup `kbcli cluster delete postgres-ywrmpr-backup --auto-approve --namespace ns-yztjr ` Cluster postgres-ywrmpr-backup deleted pod_info:postgres-ywrmpr-backup-postgresql-0 5/5 Running 0 85s postgres-ywrmpr-backup-postgresql-1 5/5 Running 0 85s pod_info:postgres-ywrmpr-backup-postgresql-0 4/5 Terminating 0 105s postgres-ywrmpr-backup-postgresql-1 4/5 Terminating 0 105s No resources found in ns-yztjr namespace. delete cluster pod done No resources found in ns-yztjr namespace. check cluster resource non-exist OK: pvc No resources found in ns-yztjr namespace. delete cluster done No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. cluster delete backup `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge backups backup-ns-yztjr-postgres-ywrmpr-20250901132750 --namespace ns-yztjr ` backup.dataprotection.kubeblocks.io/backup-ns-yztjr-postgres-ywrmpr-20250901132750 patched `kbcli cluster delete-backup postgres-ywrmpr --name backup-ns-yztjr-postgres-ywrmpr-20250901132750 --force --auto-approve --namespace ns-yztjr ` Backup backup-ns-yztjr-postgres-ywrmpr-20250901132750 deleted No opsrequests found in ns-yztjr namespace. cluster config-wal-g backup `kubectl get backuprepo backuprepo-kbcli-test -o jsonpath="***.spec.credential.name***"` `kubectl get backuprepo backuprepo-kbcli-test -o jsonpath="***.spec.credential.namespace***"` `kubectl get secrets kb-backuprepo-bxwnt -n kb-hmwej -o jsonpath="***.data.accessKeyId***"` `kubectl get secrets kb-backuprepo-bxwnt -n kb-hmwej -o jsonpath="***.data.secretAccessKey***"` KUBEBLOCKS NAMESPACE:kb-hmwej get kubeblocks namespace done `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-hmwej -o jsonpath="***.items[0].data.root-user***"` `kubectl get secrets -l app.kubernetes.io/instance=kbcli-test-minio --namespace kb-hmwej -o jsonpath="***.items[0].data.root-password***"` minio_user:kbclitest,minio_password:kbclitest,minio_endpoint:kbcli-test-minio.kb-hmwej.svc.cluster.local:9000 list minio bucket kbcli-test `echo 'mc config host add minioserver http://kbcli-test-minio.kb-hmwej.svc.cluster.local:9000 kbclitest kbclitest;mc ls minioserver' | kubectl exec -it kbcli-test-minio-669d87677b-7sjlg --namespace kb-hmwej -- bash` Unable to use a TTY - input is not a terminal or the right kind of file list minio bucket done default backuprepo:backuprepo-kbcli-test exists `kbcli cluster backup postgres-ywrmpr --method config-wal-g --namespace ns-yztjr ` Backup backup-ns-yztjr-postgres-ywrmpr-20250901133022 created successfully, you can view the progress: kbcli cluster list-backups --name=backup-ns-yztjr-postgres-ywrmpr-20250901133022 -n ns-yztjr check backup status `kbcli cluster list-backups postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE SOURCE-CLUSTER METHOD STATUS TOTAL-SIZE DURATION CREATE-TIME COMPLETION-TIME EXPIRATION backup-ns-yztjr-postgres-ywrmpr-20250901133022 ns-yztjr postgres-ywrmpr config-wal-g Sep 01,2025 13:30 UTC+0800 backup_status:postgres-ywrmpr-config-wal-g-Running backup_status:postgres-ywrmpr-config-wal-g-Running backup_status:postgres-ywrmpr-config-wal-g-Running check backup status done backup_status:backup-ns-yztjr-postgres-ywrmpr-20250901133022 ns-yztjr postgres-ywrmpr config-wal-g Completed 12s Sep 01,2025 13:30 UTC+0800 Sep 01,2025 13:30 UTC+0800 cluster delete backup `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge backups backup-ns-yztjr-postgres-ywrmpr-20250901133022 --namespace ns-yztjr ` backup.dataprotection.kubeblocks.io/backup-ns-yztjr-postgres-ywrmpr-20250901133022 patched `kbcli cluster delete-backup postgres-ywrmpr --name backup-ns-yztjr-postgres-ywrmpr-20250901133022 --force --auto-approve --namespace ns-yztjr ` Backup backup-ns-yztjr-postgres-ywrmpr-20250901133022 deleted `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests backup-ns-yztjr-postgres-ywrmpr-20250901133022 --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/backup-ns-yztjr-postgres-ywrmpr-20250901133022 patched `kbcli cluster delete-ops --name backup-ns-yztjr-postgres-ywrmpr-20250901133022 --force --auto-approve --namespace ns-yztjr ` OpsRequest backup-ns-yztjr-postgres-ywrmpr-20250901133022 deleted cluster configure component_tmp: postgresql check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster configure postgres-ywrmpr --auto-approve --force=true --set archive_command="'envdir /home/postgres/pgdata/wal-g/env /home/postgres/pgdata/wal-g/wal-g wal-push %p'" --components postgresql --config-spec postgresql-configuration --config-file postgresql.conf --namespace ns-yztjr ` Will updated configure file meta: ConfigSpec: postgresql-configuration ConfigFile: postgresql.conf ComponentName: postgresql ClusterName: postgres-ywrmpr OpsRequest postgres-ywrmpr-reconfiguring-dfnsg created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-reconfiguring-dfnsg -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-reconfiguring-dfnsg ns-yztjr Reconfiguring postgres-ywrmpr postgresql Pending -/- Sep 01,2025 13:30 UTC+0800 ops_status:postgres-ywrmpr-reconfiguring-dfnsg ns-yztjr Reconfiguring postgres-ywrmpr postgresql Creating -/- Sep 01,2025 13:30 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:02 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:02 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-reconfiguring-dfnsg ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 13:30 UTC+0800 check ops status done ops_status:postgres-ywrmpr-reconfiguring-dfnsg ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 13:30 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-reconfiguring-dfnsg --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-reconfiguring-dfnsg patched `kbcli cluster delete-ops --name postgres-ywrmpr-reconfiguring-dfnsg --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-reconfiguring-dfnsg deleted check config variables Unable to use a TTY - input is not a terminal or the right kind of file current value_actual: envdir/home/postgres/pgdata/wal-g/env/home/postgres/pgdata/wal-g/wal-gwal-push%p configure:[archive_command] result actual:[envdir/home/postgres/pgdata/wal-g/env/home/postgres/pgdata/wal-g/wal-gwal-push%p] equal expected:[envdir/home/postgres/pgdata/wal-g/env/home/postgres/pgdata/wal-g/wal-gwal-push%p] `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success `kubectl get backupschedule -l app.kubernetes.io/instance=postgres-ywrmpr ` `kubectl get backupschedule postgres-ywrmpr-postgresql-backup-schedule -ojsonpath='***.spec.schedules[*].backupMethod***' ` backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched (no change) backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched backupschedule.dataprotection.kubeblocks.io/postgres-ywrmpr-postgresql-backup-schedule patched delete cluster postgres-ywrmpr-backup `kbcli cluster delete postgres-ywrmpr-backup --auto-approve --namespace ns-yztjr ` Cluster postgres-ywrmpr-backup deleted pod_info:postgres-ywrmpr-backup-postgresql-0 4/5 Running 0 6m49s postgres-ywrmpr-backup-postgresql-1 4/5 Running 0 6m49s pod_info:postgres-ywrmpr-backup-postgresql-0 3/5 Terminating 0 7m9s postgres-ywrmpr-backup-postgresql-1 3/5 Terminating 0 7m9s No resources found in ns-yztjr namespace. delete cluster pod done No resources found in ns-yztjr namespace. check cluster resource non-exist OK: pvc No resources found in ns-yztjr namespace. delete cluster done No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. cluster delete backup `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge backups 49aa172b-postgres-ywrmpr-postg-wal-g-archive --namespace ns-yztjr ` backup.dataprotection.kubeblocks.io/49aa172b-postgres-ywrmpr-postg-wal-g-archive patched `kbcli cluster delete-backup postgres-ywrmpr --name 49aa172b-postgres-ywrmpr-postg-wal-g-archive --force --auto-approve --namespace ns-yztjr ` Backup 49aa172b-postgres-ywrmpr-postg-wal-g-archive deleted `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge backups backup-ns-yztjr-postgres-ywrmpr-20250901133106 --namespace ns-yztjr ` backup.dataprotection.kubeblocks.io/backup-ns-yztjr-postgres-ywrmpr-20250901133106 patched `kbcli cluster delete-backup postgres-ywrmpr --name backup-ns-yztjr-postgres-ywrmpr-20250901133106 --force --auto-approve --namespace ns-yztjr ` Backup backup-ns-yztjr-postgres-ywrmpr-20250901133106 deleted cluster list-logs `kbcli cluster list-logs postgres-ywrmpr --namespace ns-yztjr ` No log files found. You can enable the log feature with the kbcli command below. kbcli cluster update postgres-ywrmpr --enable-all-logs=true --namespace ns-yztjr Error from server (NotFound): pods "postgres-ywrmpr-postgresql-0" not found cluster logs `kbcli cluster logs postgres-ywrmpr --tail 30 --namespace ns-yztjr ` Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) 2025-09-01 06:13:40,251 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:13:50,249 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:14:00,250 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:14:01.125 UTC [57] LOG ***ticks: 0, maint: 0, retry: 0*** 2025-09-01 06:14:10,251 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:14:20,248 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:14:30,254 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:14:31.126 UTC [57] LOG ***ticks: 0, maint: 0, retry: 0*** 2025-09-01 06:14:40,250 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:14:50,248 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:15:00,248 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:15:01.156 UTC [57] LOG ***ticks: 0, maint: 0, retry: 0*** 2025-09-01 06:15:10,254 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:15:13,823 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:15:13,829 INFO: Changed archive_command from envdir /home/postgres/pgdata/wal-g/env /home/postgres/pgdata/wal-g/wal-g wal-push %p to /bin/true 2025-09-01 06:15:13,829 INFO: Changed tcp_keepalives_idle from 0 to 45s 2025-09-01 06:15:13,829 INFO: Changed tcp_keepalives_interval from 0 to 10s 2025-09-01 06:15:13,831 INFO: Reloading PostgreSQL configuration. server signaled 2025-09-01 06:15:14,850 INFO: No local configuration items changed. 2025-09-01 06:15:14,914 INFO: Changed tcp_keepalives_idle from 0 to 45s 2025-09-01 06:15:14,914 INFO: Changed tcp_keepalives_interval from 0 to 10s 2025-09-01 06:15:14,916 INFO: Reloading PostgreSQL configuration. server signaled 2025-09-01 06:15:15,933 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:15:25,351 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:15:31.154 UTC [57] LOG ***ticks: 0, maint: 0, retry: 0*** 2025-09-01 06:15:35,358 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:15:45,515 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock 2025-09-01 06:15:55,360 INFO: no action. I am (postgres-ywrmpr-postgresql-0), the leader with the lock cluster logs running `kbcli cluster logs postgres-ywrmpr --tail 30 --file-type=running --namespace ns-yztjr ` error: get pod component definition name in cluster.yaml fail cluster expose check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster expose postgres-ywrmpr --auto-approve --force=true --type vpc --enable false --components postgresql --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-expose-v2k9b created successfully, you can view the progress: kbcli cluster describe-ops postgres-ywrmpr-expose-v2k9b -n ns-yztjr check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wxd69 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 13:31 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-hxzkb ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 14:15 UTC+0800 postgres-ywrmpr-expose-v2k9b ns-yztjr Expose postgres-ywrmpr Pending -/- Sep 01,2025 14:16 UTC+0800 ops_status:postgres-ywrmpr-expose-v2k9b ns-yztjr Expose postgres-ywrmpr Creating -/- Sep 01,2025 14:16 UTC+0800 check cluster status `kbcli cluster list postgres-ywrmpr --show-labels --namespace ns-yztjr ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS postgres-ywrmpr ns-yztjr postgresql WipeOut Running Sep 01,2025 11:23 UTC+0800 app.kubernetes.io/instance=postgres-ywrmpr,clusterdefinition.kubeblocks.io/name=postgresql,clusterversion.kubeblocks.io/name= check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances postgres-ywrmpr --namespace ns-yztjr ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME postgres-ywrmpr-postgresql-0 ns-yztjr postgres-ywrmpr postgresql Running primary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000006/10.224.0.10 Sep 01,2025 13:02 UTC+0800 postgres-ywrmpr-postgresql-1 ns-yztjr postgres-ywrmpr postgresql Running secondary 0 200m / 200m 644245094400m / 644245094400m data:4Gi aks-cicdamdpool-38368475-vmss000008/10.224.0.9 Sep 01,2025 13:02 UTC+0800 check pod status done check cluster role check cluster role done primary: postgres-ywrmpr-postgresql-0;secondary: postgres-ywrmpr-postgresql-1 check cluster connect `echo '' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr` check cluster connect done check ops status `kbcli cluster list-ops postgres-ywrmpr --status all --namespace ns-yztjr ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME postgres-ywrmpr-postgresql-backup-schedule-wxd69 ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 13:31 UTC+0800 postgres-ywrmpr-postgresql-backup-schedule-hxzkb ns-yztjr Reconfiguring postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 14:15 UTC+0800 postgres-ywrmpr-expose-v2k9b ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 14:16 UTC+0800 ops_status:postgres-ywrmpr-expose-v2k9b ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 14:16 UTC+0800 ops_status:postgres-ywrmpr-expose-v2k9b ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 14:16 UTC+0800 ops_status:postgres-ywrmpr-expose-v2k9b ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 14:16 UTC+0800 ops_status:postgres-ywrmpr-expose-v2k9b ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 14:16 UTC+0800 ops_status:postgres-ywrmpr-expose-v2k9b ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 14:16 UTC+0800 ops_status:postgres-ywrmpr-expose-v2k9b ns-yztjr Expose postgres-ywrmpr postgresql Running 0/1 Sep 01,2025 14:16 UTC+0800 check ops status done ops_status:postgres-ywrmpr-expose-v2k9b ns-yztjr Expose postgres-ywrmpr postgresql Succeed 1/1 Sep 01,2025 14:16 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests postgres-ywrmpr-expose-v2k9b --namespace ns-yztjr ` opsrequest.apps.kubeblocks.io/postgres-ywrmpr-expose-v2k9b patched `kbcli cluster delete-ops --name postgres-ywrmpr-expose-v2k9b --force --auto-approve --namespace ns-yztjr ` OpsRequest postgres-ywrmpr-expose-v2k9b deleted `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kbcli cluster connect postgres-ywrmpr --namespace ns-yztjr ` check data: Connect to instance postgres-ywrmpr-postgresql-0: out of postgres-ywrmpr-postgresql-0(primary), postgres-ywrmpr-postgresql-1(secondary) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster data consistent Success `echo 'SELECT value FROM tmp_table WHERE id = 1;' | kubectl exec -it postgres-ywrmpr-postgresql-1 --namespace ns-yztjr -- psql -U postgres ` check readonly data: Defaulted container "postgresql" out of: postgresql, pgbouncer, exporter, lorry, config-manager, pg-init-container (init), init-lorry (init) Unable to use a TTY - input is not a terminal or the right kind of file value ------- fxsvi (1 row) check cluster readonly data consistent Success check db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-0 -n ns-yztjr -- psql -U postgres -d executions_loop ` check db_client batch data Success check readonly db_client batch data count `echo "select count(*) from executions_loop_table;" | kubectl exec -it postgres-ywrmpr-postgresql-1 -n ns-yztjr -- psql -U postgres -d executions_loop ` check readonly db_client batch data Success delete cluster postgres-ywrmpr `kbcli cluster delete postgres-ywrmpr --auto-approve --namespace ns-yztjr ` Cluster postgres-ywrmpr deleted pod_info:postgres-ywrmpr-postgresql-0 5/5 Running 1 (71m ago) 73m postgres-ywrmpr-postgresql-1 5/5 Running 0 73m pod_info:postgres-ywrmpr-postgresql-0 4/5 Terminating 1 (72m ago) 74m postgres-ywrmpr-postgresql-1 4/5 Terminating 0 74m No resources found in ns-yztjr namespace. delete cluster pod done No resources found in ns-yztjr namespace. check cluster resource non-exist OK: pvc No resources found in ns-yztjr namespace. delete cluster done No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. No resources found in ns-yztjr namespace. Postgresql Test Suite All Done! --------------------------------------Postgresql (Topology = replication Replicas 2) Test Result-------------------------------------- [PASSED]|[Create]|[ComponentVersion=postgresql;ServiceVersion=12.14.0;]|[Description=Create a cluster and component version postgresql and service version 12.14.0] [PASSED]|[Connect]|[ComponentName=postgresql]|[Description=Connect to the cluster] [PASSED]|[AddData]|[Values=fxsvi]|[Description=Add data to the cluster] [PASSED]|[CheckAddDataReadonly]|[Values=fxsvi;Role=Readonly]|[Description=Add data to the cluster readonly] [PASSED]|[Expose]|[Enable=true;TYPE=vpc;ComponentName=postgresql]|[Description=Expose Enable the vpc service with postgresql component] [PASSED]|[Restart]|[-]|[Description=Restart the cluster] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Backup]|[BackupMethod=pg-basebackup]|[Description=The cluster pg-basebackup Backup] [PASSED]|[Restore To Time]|[BackupMethod=pg-basebackup]|[Description=The cluster pg-basebackup Restore To Time] [PASSED]|[Connect]|[ComponentName=postgresql]|[Description=Connect to the cluster] [PASSED]|[Delete Restore Cluster]|[BackupMethod=pg-basebackup]|[Description=Delete the pg-basebackup restore cluster] [PASSED]|[Upgrade]|[ComponentName=postgresql;ComponentVersionFrom=12.14.0;ComponentVersionTo=12.22.0]|[Description=Upgrade the cluster specify component postgresql service version from 12.14.0 to 12.22.0] [PASSED]|[Upgrade]|[ComponentName=postgresql;ComponentVersionFrom=12.22.0;ComponentVersionTo=12.14.0]|[Description=Upgrade the cluster specify component postgresql service version from 12.22.0 to 12.14.0] [PASSED]|[Upgrade]|[ComponentName=postgresql;ComponentVersionFrom=12.14.0;ComponentVersionTo=12.14.1]|[Description=Upgrade the cluster specify component postgresql service version from 12.14.0 to 12.14.1] [PASSED]|[Upgrade]|[ComponentName=postgresql;ComponentVersionFrom=12.14.1;ComponentVersionTo=12.22.0]|[Description=Upgrade the cluster specify component postgresql service version from 12.14.1 to 12.22.0] [PASSED]|[Upgrade]|[ComponentName=postgresql;ComponentVersionFrom=12.22.0;ComponentVersionTo=12.14.1]|[Description=Upgrade the cluster specify component postgresql service version from 12.22.0 to 12.14.1] [PASSED]|[Upgrade]|[ComponentName=postgresql;ComponentVersionFrom=12.14.1;ComponentVersionTo=12.15.0]|[Description=Upgrade the cluster specify component postgresql service version from 12.14.1 to 12.15.0] [PASSED]|[Upgrade]|[ComponentName=postgresql;ComponentVersionFrom=12.15.0;ComponentVersionTo=12.22.0]|[Description=Upgrade the cluster specify component postgresql service version from 12.15.0 to 12.22.0] [PASSED]|[Upgrade]|[ComponentName=postgresql;ComponentVersionFrom=12.22.0;ComponentVersionTo=12.15.0]|[Description=Upgrade the cluster specify component postgresql service version from 12.22.0 to 12.15.0] [PASSED]|[Upgrade]|[ComponentName=postgresql;ComponentVersionFrom=12.15.0;ComponentVersionTo=12.14.0]|[Description=Upgrade the cluster specify component postgresql service version from 12.15.0 to 12.14.0] [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=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]|[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]|[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]|[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]|[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]|[VerticalScaling]|[ComponentName=postgresql]|[Description=VerticalScaling the cluster specify component postgresql] [PASSED]|[Failover]|[HA=Evicting Pod;ComponentName=postgresql]|[Description=Simulates conditions where pods evicting either due to node drained thereby testing the application's resilience to unavailability of some replicas due to evicting.] [PASSED]|[Reconfiguring]|[ComponentName=postgresql;max_connections=200]|[Description=Reconfiguring the cluster specify component postgresql set max_connections=200] [PASSED]|[Failover]|[HA=Pod Kill;ComponentName=postgresql]|[Description=Simulates conditions where pods experience kill for a period of time either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to kill.] [PASSED]|[Reconfiguring]|[ComponentName=postgresql;shared_buffers=512MB]|[Description=Reconfiguring the cluster specify component postgresql set shared_buffers=512MB] [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 Bandwidth;Durations=2m;ComponentName=postgresql]|[Description=Simulates network bandwidth fault thereby testing the application's resilience to potential slowness/unavailability of some replicas due to bandwidth network.] [PASSED]|[Failover]|[HA=IOChaos Fault;ErrNO=16;ErrMessage=Device or resource busy;Durations=2m;]|[Description=Simulates conditions where pods experience IO faults either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to IO faults.] [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]|[No-Failover]|[HA=IOChaos AttrOverride;Durations=2m;]|[Description=Simulates conditions where pods experience IO attribute override faults either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to IO attribute override.] [PASSED]|[No-Failover]|[HA=IOChaos Mistake;Durations=2m;]|[Description=Simulates conditions where pods experience IO mistake faults either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to IO mistake faults.] [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]|[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=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]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [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=Connection Stress;ComponentName=postgresql]|[Description=Simulates conditions where pods experience connection stress either due to expected/undesired processes thereby testing the application's resilience to potential slowness/unavailability of some replicas due to high Connection load.] [PASSED]|[Update]|[Logs=Enable]|[Description=Update the cluster Logs enable] [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]|[VolumeExpansion]|[ComponentName=postgresql]|[Description=VolumeExpansion the cluster specify component postgresql] [PASSED]|[SwitchOver]|[ComponentName=postgresql]|[Description=SwitchOver 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]|[Backup]|[BackupMethod=pg-basebackup]|[Description=The cluster pg-basebackup Backup] [PASSED]|[Restore]|[BackupMethod=pg-basebackup]|[Description=The cluster pg-basebackup Restore] [PASSED]|[Connect]|[ComponentName=postgresql]|[Description=Connect to the cluster] [PASSED]|[Delete Restore Cluster]|[BackupMethod=pg-basebackup]|[Description=Delete the pg-basebackup restore cluster] [PASSED]|[RebuildInstance]|[ComponentName=postgresql]|[Description=Rebuild the cluster instance specify component postgresql] [PASSED]|[Backup]|[Schedule=true;BackupMethod=pg-basebackup]|[Description=The cluster Schedule pg-basebackup Backup] [PASSED]|[Restore]|[Schedule=true;BackupMethod=pg-basebackup]|[Description=The cluster Schedule pg-basebackup Restore] [PASSED]|[Connect]|[ComponentName=postgresql]|[Description=Connect to the cluster] [PASSED]|[Delete Restore Cluster]|[Schedule=true;BackupMethod=pg-basebackup]|[Description=Delete the Schedule pg-basebackup restore cluster] [PASSED]|[Backup]|[BackupMethod=volume-snapshot]|[Description=The cluster volume-snapshot Backup] [PASSED]|[Restore]|[BackupMethod=volume-snapshot]|[Description=The cluster volume-snapshot Restore] [PASSED]|[Connect]|[ComponentName=postgresql]|[Description=Connect to the cluster] [PASSED]|[Delete Restore Cluster]|[BackupMethod=volume-snapshot]|[Description=Delete the volume-snapshot restore cluster] [PASSED]|[Backup]|[BackupMethod=config-wal-g]|[Description=The cluster config-wal-g Backup] [PASSED]|[Reconfiguring]|[ComponentName=postgresql;archive_command="'envdir /home/postgres/pgdata/wal-g/env /home/postgres/pgdata/wal-g/wal-g wal-push %p'"]|[Description=Reconfiguring the cluster specify component postgresql set archive_command="'envdir /home/postgres/pgdata/wal-g/env /home/postgres/pgdata/wal-g/wal-g wal-push %p'"] [PASSED]|[Expose]|[Disable=true;TYPE=vpc;ComponentName=postgresql]|[Description=Expose Disable the vpc service with postgresql component] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]