source commons files source engines files source kubeblocks files `kubectl get namespace | grep ns-xzacs ` `kubectl create namespace ns-xzacs` namespace/ns-xzacs created create namespace ns-xzacs 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.4-beta.1` Your system is linux_amd64 Installing kbcli ... Downloading ... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 32.1M 100 32.1M 0 0 107M 0 --:--:-- --:--:-- --:--:-- 107M kbcli installed successfully. Kubernetes: v1.32.5-eks-5d4a308 KubeBlocks: 0.9.4 kbcli: 0.9.4-beta.1 WARNING: version difference between kbcli (0.9.4-beta.1) and kubeblocks (0.9.4) 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.4-beta.1 done Kubernetes: v1.32.5-eks-5d4a308 KubeBlocks: 0.9.4 kbcli: 0.9.4-beta.1 WARNING: version difference between kbcli (0.9.4-beta.1) and kubeblocks (0.9.4) Kubernetes Env: v1.32.5-eks-5d4a308 POD_RESOURCES: No resources found found default storage class: gp3 kubeblocks version is:0.9.4 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:dmdb set component version No resources found no component version found unsupported component definition not found component version set replicas first:1 set replicas third:1 set minimum cmpv service version set minimum cmpv service version replicas:1 REPORT_COUNT:1 CLUSTER_TOPOLOGY: Not found topology in cluster definition dmdb LIMIT_CPU:0.1 LIMIT_MEMORY:0.5 storage size: 1 No resources found in ns-xzacs namespace. termination_policy:Halt create 1 replica Halt dmdb cluster check cluster version check cluster definition `kbcli cluster create dmdb-yleewj --termination-policy=Halt --cluster-definition=dmdb --enable-all-logs=false --cluster-version=dmdb-0.1.0 --set cpu=100m,memory=0.5Gi,replicas=1,storage=1Gi --namespace ns-xzacs ` Cluster dmdb-yleewj created check cluster status `kbcli cluster list dmdb-yleewj --show-labels --namespace ns-xzacs ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS dmdb-yleewj ns-xzacs dmdb dmdb-0.1.0 Halt Jun 19,2025 18:13 UTC+0800 clusterdefinition.kubeblocks.io/name=dmdb,clusterversion.kubeblocks.io/name=dmdb-0.1.0 cluster_status:Creating cluster_status:Creating check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances dmdb-yleewj --namespace ns-xzacs ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME dmdb-yleewj-dmdb-0 ns-xzacs dmdb-yleewj dmdb Running us-west-2a 100m / 100m 512Mi / 512Mi data:1Gi ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:13 UTC+0800 check pod status done connect unsupported engine type: dmdb `kubectl get secrets -l app.kubernetes.io/instance=dmdb-yleewj` `kubectl get secrets dmdb-yleewj-conn-credential -o jsonpath="***.data.username***"` `kubectl get secrets dmdb-yleewj-conn-credential -o jsonpath="***.data.password***"` `kubectl get secrets dmdb-yleewj-conn-credential -o jsonpath="***.data.port***"` DB_USERNAME:MONITOR;DB_PASSWORD:4fls6d8k;DB_PORT:5236;DB_DATABASE: check pod dmdb-yleewj-dmdb-0 container_name dmdb exist password 4fls6d8k check pod dmdb-yleewj-dmdb-0 container_name exporter exist password 4fls6d8k No container logs contain secret password. describe cluster `kbcli cluster describe dmdb-yleewj --namespace ns-xzacs ` Name: dmdb-yleewj Created Time: Jun 19,2025 18:13 UTC+0800 NAMESPACE CLUSTER-DEFINITION VERSION STATUS TERMINATION-POLICY ns-xzacs dmdb dmdb-0.1.0 Running Halt Endpoints: COMPONENT MODE INTERNAL EXTERNAL dmdb ReadWrite dmdb-yleewj-dmdb.ns-xzacs.svc.cluster.local:5236 dmdb-yleewj-dmdb.ns-xzacs.svc.cluster.local:4236 Topology: COMPONENT INSTANCE ROLE STATUS AZ NODE CREATED-TIME dmdb dmdb-yleewj-dmdb-0 Running us-west-2a ip-172-31-10-91.us-west-2.compute.internal/172.31.10.91 Jun 19,2025 18:13 UTC+0800 Resources Allocation: COMPONENT DEDICATED CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE-SIZE STORAGE-CLASS dmdb false 100m / 100m 512Mi / 512Mi data:1Gi kb-default-sc Images: COMPONENT TYPE IMAGE dmdb dmdb docker.io/apecloud/dm8_single:0.1.0 Show cluster events: kbcli cluster list-events -n ns-xzacs dmdb-yleewj `kbcli cluster label dmdb-yleewj app.kubernetes.io/instance- --namespace ns-xzacs ` label "app.kubernetes.io/instance" not found. `kbcli cluster label dmdb-yleewj app.kubernetes.io/instance=dmdb-yleewj --namespace ns-xzacs ` `kbcli cluster label dmdb-yleewj --list --namespace ns-xzacs ` NAME NAMESPACE LABELS dmdb-yleewj ns-xzacs app.kubernetes.io/instance=dmdb-yleewj clusterdefinition.kubeblocks.io/name=dmdb clusterversion.kubeblocks.io/name=dmdb-0.1.0 label cluster app.kubernetes.io/instance=dmdb-yleewj Success `kbcli cluster label case.name=kbcli.test1 -l app.kubernetes.io/instance=dmdb-yleewj --namespace ns-xzacs ` `kbcli cluster label dmdb-yleewj --list --namespace ns-xzacs ` NAME NAMESPACE LABELS dmdb-yleewj ns-xzacs app.kubernetes.io/instance=dmdb-yleewj case.name=kbcli.test1 clusterdefinition.kubeblocks.io/name=dmdb clusterversion.kubeblocks.io/name=dmdb-0.1.0 label cluster case.name=kbcli.test1 Success `kbcli cluster label dmdb-yleewj case.name=kbcli.test2 --overwrite --namespace ns-xzacs ` `kbcli cluster label dmdb-yleewj --list --namespace ns-xzacs ` NAME NAMESPACE LABELS dmdb-yleewj ns-xzacs app.kubernetes.io/instance=dmdb-yleewj case.name=kbcli.test2 clusterdefinition.kubeblocks.io/name=dmdb clusterversion.kubeblocks.io/name=dmdb-0.1.0 label cluster case.name=kbcli.test2 Success `kbcli cluster label dmdb-yleewj case.name- --namespace ns-xzacs ` `kbcli cluster label dmdb-yleewj --list --namespace ns-xzacs ` NAME NAMESPACE LABELS dmdb-yleewj ns-xzacs app.kubernetes.io/instance=dmdb-yleewj clusterdefinition.kubeblocks.io/name=dmdb clusterversion.kubeblocks.io/name=dmdb-0.1.0 delete cluster label case.name Success cluster connect kbcli unsupported engine type: dmdb cluster vscale check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster vscale dmdb-yleewj --auto-approve --force=true --components dmdb --cpu 200m --memory 0.6Gi --namespace ns-xzacs ` OpsRequest dmdb-yleewj-verticalscaling-b56gh created successfully, you can view the progress: kbcli cluster describe-ops dmdb-yleewj-verticalscaling-b56gh -n ns-xzacs check ops status `kbcli cluster list-ops dmdb-yleewj --status all --namespace ns-xzacs ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME dmdb-yleewj-verticalscaling-b56gh ns-xzacs VerticalScaling dmdb-yleewj dmdb Running 0/1 Jun 19,2025 18:14 UTC+0800 check cluster status `kbcli cluster list dmdb-yleewj --show-labels --namespace ns-xzacs ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS dmdb-yleewj ns-xzacs dmdb dmdb-0.1.0 Halt Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=dmdb-yleewj,clusterdefinition.kubeblocks.io/name=dmdb,clusterversion.kubeblocks.io/name=dmdb-0.1.0 cluster_status:Updating 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 dmdb-yleewj --namespace ns-xzacs ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME dmdb-yleewj-dmdb-0 ns-xzacs dmdb-yleewj dmdb Running us-west-2a 200m / 200m 644245094400m / 644245094400m data:1Gi ip-172-31-8-193.us-west-2.compute.internal/172.31.8.193 Jun 19,2025 18:14 UTC+0800 check pod status done connect unsupported engine type: dmdb check ops status `kbcli cluster list-ops dmdb-yleewj --status all --namespace ns-xzacs ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME dmdb-yleewj-verticalscaling-b56gh ns-xzacs VerticalScaling dmdb-yleewj dmdb Succeed 1/1 Jun 19,2025 18:14 UTC+0800 check ops status done ops_status:dmdb-yleewj-verticalscaling-b56gh ns-xzacs VerticalScaling dmdb-yleewj dmdb Succeed 1/1 Jun 19,2025 18:14 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests dmdb-yleewj-verticalscaling-b56gh --namespace ns-xzacs ` opsrequest.apps.kubeblocks.io/dmdb-yleewj-verticalscaling-b56gh patched `kbcli cluster delete-ops --name dmdb-yleewj-verticalscaling-b56gh --force --auto-approve --namespace ns-xzacs ` OpsRequest dmdb-yleewj-verticalscaling-b56gh deleted cluster stop check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster stop dmdb-yleewj --auto-approve --force=true --namespace ns-xzacs ` OpsRequest dmdb-yleewj-stop-9zwqs created successfully, you can view the progress: kbcli cluster describe-ops dmdb-yleewj-stop-9zwqs -n ns-xzacs check ops status `kbcli cluster list-ops dmdb-yleewj --status all --namespace ns-xzacs ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME dmdb-yleewj-stop-9zwqs ns-xzacs Stop dmdb-yleewj dmdb Running 0/1 Jun 19,2025 18:15 UTC+0800 check cluster status `kbcli cluster list dmdb-yleewj --show-labels --namespace ns-xzacs ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS dmdb-yleewj ns-xzacs dmdb dmdb-0.1.0 Halt Stopping Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=dmdb-yleewj,clusterdefinition.kubeblocks.io/name=dmdb,clusterversion.kubeblocks.io/name=dmdb-0.1.0 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 dmdb-yleewj --namespace ns-xzacs ` 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 dmdb-yleewj --status all --namespace ns-xzacs ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME dmdb-yleewj-stop-9zwqs ns-xzacs Stop dmdb-yleewj dmdb Succeed 1/1 Jun 19,2025 18:15 UTC+0800 check ops status done ops_status:dmdb-yleewj-stop-9zwqs ns-xzacs Stop dmdb-yleewj dmdb Succeed 1/1 Jun 19,2025 18:15 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests dmdb-yleewj-stop-9zwqs --namespace ns-xzacs ` opsrequest.apps.kubeblocks.io/dmdb-yleewj-stop-9zwqs patched `kbcli cluster delete-ops --name dmdb-yleewj-stop-9zwqs --force --auto-approve --namespace ns-xzacs ` OpsRequest dmdb-yleewj-stop-9zwqs deleted cluster start check cluster status before ops check cluster status done cluster_status:Stopped `kbcli cluster start dmdb-yleewj --force=true --namespace ns-xzacs ` OpsRequest dmdb-yleewj-start-pdrq6 created successfully, you can view the progress: kbcli cluster describe-ops dmdb-yleewj-start-pdrq6 -n ns-xzacs check ops status `kbcli cluster list-ops dmdb-yleewj --status all --namespace ns-xzacs ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME dmdb-yleewj-start-pdrq6 ns-xzacs Start dmdb-yleewj Creating -/- Jun 19,2025 18:16 UTC+0800 check cluster status `kbcli cluster list dmdb-yleewj --show-labels --namespace ns-xzacs ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS dmdb-yleewj ns-xzacs dmdb dmdb-0.1.0 Halt Running Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=dmdb-yleewj,clusterdefinition.kubeblocks.io/name=dmdb,clusterversion.kubeblocks.io/name=dmdb-0.1.0 check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances dmdb-yleewj --namespace ns-xzacs ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME dmdb-yleewj-dmdb-0 ns-xzacs dmdb-yleewj dmdb Running us-west-2a 200m / 200m 644245094400m / 644245094400m data:1Gi ip-172-31-8-193.us-west-2.compute.internal/172.31.8.193 Jun 19,2025 18:16 UTC+0800 check pod status done connect unsupported engine type: dmdb check ops status `kbcli cluster list-ops dmdb-yleewj --status all --namespace ns-xzacs ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME dmdb-yleewj-start-pdrq6 ns-xzacs Start dmdb-yleewj dmdb Succeed 1/1 Jun 19,2025 18:16 UTC+0800 check ops status done ops_status:dmdb-yleewj-start-pdrq6 ns-xzacs Start dmdb-yleewj dmdb Succeed 1/1 Jun 19,2025 18:16 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests dmdb-yleewj-start-pdrq6 --namespace ns-xzacs ` opsrequest.apps.kubeblocks.io/dmdb-yleewj-start-pdrq6 patched `kbcli cluster delete-ops --name dmdb-yleewj-start-pdrq6 --force --auto-approve --namespace ns-xzacs ` OpsRequest dmdb-yleewj-start-pdrq6 deleted `kubectl get pvc -l app.kubernetes.io/instance=dmdb-yleewj,apps.kubeblocks.io/component-name=dmdb,apps.kubeblocks.io/vct-name=data --namespace ns-xzacs ` cluster volume-expand check cluster status before ops check cluster status done cluster_status:Running No resources found in dmdb-yleewj namespace. `kbcli cluster volume-expand dmdb-yleewj --auto-approve --force=true --components dmdb --volume-claim-templates data --storage 2Gi --namespace ns-xzacs ` OpsRequest dmdb-yleewj-volumeexpansion-lcmdc created successfully, you can view the progress: kbcli cluster describe-ops dmdb-yleewj-volumeexpansion-lcmdc -n ns-xzacs check ops status `kbcli cluster list-ops dmdb-yleewj --status all --namespace ns-xzacs ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME dmdb-yleewj-volumeexpansion-lcmdc ns-xzacs VolumeExpansion dmdb-yleewj dmdb Running 0/1 Jun 19,2025 18:16 UTC+0800 check cluster status `kbcli cluster list dmdb-yleewj --show-labels --namespace ns-xzacs ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS dmdb-yleewj ns-xzacs dmdb dmdb-0.1.0 Halt Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=dmdb-yleewj,clusterdefinition.kubeblocks.io/name=dmdb,clusterversion.kubeblocks.io/name=dmdb-0.1.0 cluster_status:Updating 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 dmdb-yleewj --namespace ns-xzacs ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME dmdb-yleewj-dmdb-0 ns-xzacs dmdb-yleewj dmdb Running us-west-2a 200m / 200m 644245094400m / 644245094400m data:2Gi ip-172-31-8-193.us-west-2.compute.internal/172.31.8.193 Jun 19,2025 18:16 UTC+0800 check pod status done connect unsupported engine type: dmdb No resources found in dmdb-yleewj namespace. check ops status `kbcli cluster list-ops dmdb-yleewj --status all --namespace ns-xzacs ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME dmdb-yleewj-volumeexpansion-lcmdc ns-xzacs VolumeExpansion dmdb-yleewj dmdb Succeed 1/1 Jun 19,2025 18:16 UTC+0800 check ops status done ops_status:dmdb-yleewj-volumeexpansion-lcmdc ns-xzacs VolumeExpansion dmdb-yleewj dmdb Succeed 1/1 Jun 19,2025 18:16 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests dmdb-yleewj-volumeexpansion-lcmdc --namespace ns-xzacs ` opsrequest.apps.kubeblocks.io/dmdb-yleewj-volumeexpansion-lcmdc patched `kbcli cluster delete-ops --name dmdb-yleewj-volumeexpansion-lcmdc --force --auto-approve --namespace ns-xzacs ` OpsRequest dmdb-yleewj-volumeexpansion-lcmdc deleted cluster restart check cluster status before ops check cluster status done cluster_status:Running `kbcli cluster restart dmdb-yleewj --auto-approve --force=true --namespace ns-xzacs ` OpsRequest dmdb-yleewj-restart-tj2rx created successfully, you can view the progress: kbcli cluster describe-ops dmdb-yleewj-restart-tj2rx -n ns-xzacs check ops status `kbcli cluster list-ops dmdb-yleewj --status all --namespace ns-xzacs ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME dmdb-yleewj-restart-tj2rx ns-xzacs Restart dmdb-yleewj dmdb Running 0/1 Jun 19,2025 18:18 UTC+0800 check cluster status `kbcli cluster list dmdb-yleewj --show-labels --namespace ns-xzacs ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS dmdb-yleewj ns-xzacs dmdb dmdb-0.1.0 Halt Updating Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=dmdb-yleewj,clusterdefinition.kubeblocks.io/name=dmdb,clusterversion.kubeblocks.io/name=dmdb-0.1.0 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 dmdb-yleewj --namespace ns-xzacs ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME dmdb-yleewj-dmdb-0 ns-xzacs dmdb-yleewj dmdb Running us-west-2a 200m / 200m 644245094400m / 644245094400m data:2Gi ip-172-31-8-193.us-west-2.compute.internal/172.31.8.193 Jun 19,2025 18:18 UTC+0800 check pod status done connect unsupported engine type: dmdb check ops status `kbcli cluster list-ops dmdb-yleewj --status all --namespace ns-xzacs ` NAME NAMESPACE TYPE CLUSTER COMPONENT STATUS PROGRESS CREATED-TIME dmdb-yleewj-restart-tj2rx ns-xzacs Restart dmdb-yleewj dmdb Succeed 1/1 Jun 19,2025 18:18 UTC+0800 check ops status done ops_status:dmdb-yleewj-restart-tj2rx ns-xzacs Restart dmdb-yleewj dmdb Succeed 1/1 Jun 19,2025 18:18 UTC+0800 `kubectl patch -p '***"metadata":***"finalizers":[]***' --type=merge opsrequests dmdb-yleewj-restart-tj2rx --namespace ns-xzacs ` opsrequest.apps.kubeblocks.io/dmdb-yleewj-restart-tj2rx patched `kbcli cluster delete-ops --name dmdb-yleewj-restart-tj2rx --force --auto-approve --namespace ns-xzacs ` OpsRequest dmdb-yleewj-restart-tj2rx deleted cluster update terminationPolicy WipeOut `kbcli cluster update dmdb-yleewj --termination-policy=WipeOut --namespace ns-xzacs ` cluster.apps.kubeblocks.io/dmdb-yleewj updated check cluster status `kbcli cluster list dmdb-yleewj --show-labels --namespace ns-xzacs ` NAME NAMESPACE CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS CREATED-TIME LABELS dmdb-yleewj ns-xzacs dmdb dmdb-0.1.0 WipeOut Running Jun 19,2025 18:13 UTC+0800 app.kubernetes.io/instance=dmdb-yleewj,clusterdefinition.kubeblocks.io/name=dmdb,clusterversion.kubeblocks.io/name=dmdb-0.1.0 check cluster status done cluster_status:Running check pod status `kbcli cluster list-instances dmdb-yleewj --namespace ns-xzacs ` NAME NAMESPACE CLUSTER COMPONENT STATUS ROLE ACCESSMODE AZ CPU(REQUEST/LIMIT) MEMORY(REQUEST/LIMIT) STORAGE NODE CREATED-TIME dmdb-yleewj-dmdb-0 ns-xzacs dmdb-yleewj dmdb Running us-west-2a 200m / 200m 644245094400m / 644245094400m data:2Gi ip-172-31-8-193.us-west-2.compute.internal/172.31.8.193 Jun 19,2025 18:18 UTC+0800 check pod status done connect unsupported engine type: dmdb cluster list-logs `kbcli cluster list-logs dmdb-yleewj --namespace ns-xzacs ` No log files found. You can enable the log feature with the kbcli command below. kbcli cluster update dmdb-yleewj --enable-all-logs=true --namespace ns-xzacs Error from server (NotFound): pods "dmdb-yleewj-dmdb-0" not found cluster logs `kbcli cluster logs dmdb-yleewj --tail 30 --namespace ns-xzacs ` Defaulted container "dmdb" out of: dmdb, exporter Script start. file dm.key not found, use default license! License will expire on 2025-07-03 Normal of FAST Normal of DEFAULT Normal of RECYCLE Normal of KEEP Normal of ROLL log file path: /opt/dmdbms/data/DAMENG/DAMENG01.log log file path: /opt/dmdbms/data/DAMENG/DAMENG02.log write to dir [/opt/dmdbms/data/DAMENG]. create dm database success. 2025-06-19 18:18:48 initdb V8 db version: 0x7000c Init DM success! Start DmAPService... Starting DmAPService: [ OK ] /opt/dmdbms/conf/dm.ini does not exist, use default dm.ini Start DMSERVER success! Dmserver is running. DM Database is not OK, please wait... delete cluster dmdb-yleewj `kbcli cluster delete dmdb-yleewj --auto-approve --namespace ns-xzacs ` Cluster dmdb-yleewj deleted pod_info:dmdb-yleewj-dmdb-0 2/2 Terminating 0 35s pod_info:dmdb-yleewj-dmdb-0 2/2 Terminating 0 56s No resources found in ns-xzacs namespace. delete cluster pod done No resources found in ns-xzacs namespace. check cluster resource non-exist OK: pvc No resources found in ns-xzacs namespace. delete cluster done No resources found in ns-xzacs namespace. No resources found in ns-xzacs namespace. No resources found in ns-xzacs namespace. Dmdb Test Suite All Done! --------------------------------------Damengdb Ce (Topology = Replicas 1) Test Result-------------------------------------- [PASSED]|[Create]|[ClusterDefinition=dmdb;ClusterVersion=dmdb-0.1.0;]|[Description=Create a cluster with the specified cluster definition dmdb and cluster version dmdb-0.1.0] [PASSED]|[VerticalScaling]|[ComponentName=dmdb]|[Description=VerticalScaling the cluster specify component dmdb] [PASSED]|[Stop]|[-]|[Description=Stop the cluster] [PASSED]|[Start]|[-]|[Description=Start the cluster] [PASSED]|[VolumeExpansion]|[ComponentName=dmdb]|[Description=VolumeExpansion the cluster specify component dmdb] [PASSED]|[Restart]|[-]|[Description=Restart the cluster] [PASSED]|[Update]|[TerminationPolicy=WipeOut]|[Description=Update the cluster TerminationPolicy WipeOut] [PASSED]|[Delete]|[-]|[Description=Delete the cluster] [END]