[BUG] elasticsearch/apecloud-mysql/tidb cluster upgrade to v1 error
Describe the bug A clear and concise description of what the bug is. error: cluster "esearch-cluster" has unknown clusterVersion or componentDefinition, you can replace with accorrding ComponentDefinition with 1.0 api
kbcli version
Kubernetes: v1.30.4-vke.4
KubeBlocks: 1.0.0-beta.41,0.9.4-beta.10
kbcli: 1.0.0-beta.20
To Reproduce Steps to reproduce the behavior:
- create cluster elasticsearch in kb 0.9.4-beta.10
apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
name: esearch-cluster
namespace: default
annotations:
kubeblocks.io/extra-env: '{"mdit-roles":"master,data,ingest,transform","mode":"multi-node"}'
spec:
clusterDefinitionRef: elasticsearch
topology: multi-node
terminationPolicy: WipeOut
componentSpecs:
- name: master
serviceVersion: 7.7.1
serviceAccountName: kb-esearch-cluster
replicas: 2
resources:
requests:
cpu: 500m
memory: 2Gi
limits:
cpu: 500m
memory: 2Gi
volumeClaimTemplates:
- name: data
spec:
storageClassName:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- name: dit
serviceVersion: 7.7.1
serviceAccountName: kb-esearch-cluster
replicas: 2
resources:
requests:
cpu: 500m
memory: 2Gi
limits:
cpu: 500m
memory: 2Gi
volumeClaimTemplates:
- name: data
spec:
storageClassName:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- install kb 1.0.0-beta.41
- install elasticsearch addon 1.0.0-alpha.0
helm list -n kb-system-new
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /Users/huangzhangshu/.kube/config_vke_cn_kb_v1
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /Users/huangzhangshu/.kube/config_vke_cn_kb_v1
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
kb-addon-elasticsearch kb-system-new 1 2025-04-03 10:26:23.521789 +0800 CST deployed elasticsearch-1.0.0-alpha.0 8.8.2
kubeblocks kb-system-new 1 2025-04-03 10:24:37.583606 +0800 CST deployed kubeblocks-1.0.0-beta.41 1.0.0-beta.41
kubectl get cluster
NAME CLUSTER-DEFINITION TERMINATION-POLICY STATUS AGE
esearch-cluster elasticsearch WipeOut Running 20h
- See error
echo yes|kbcli cluster upgrade-to-v1 esearch-cluster
error: cluster "esearch-cluster" has unknown clusterVersion or componentDefinition, you can replace with accorrding ComponentDefinition with 1.0 api
after upgrade error cluster yaml
kubectl get cluster esearch-cluster -oyaml
apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
annotations:
kb-increment-converter: '{"spec":{"clusterDefinitionRef":"elasticsearch","terminationPolicy":"WipeOut","resources":{"cpu":"0","memory":"0"},"storage":{"size":"0"},"components":{"dit":{},"master":{}}},"status":{"components":{"dit":{"podsReady":true,"podsReadyTime":"2025-04-02T06:59:16Z"},"master":{"podsReady":true,"podsReadyTime":"2025-04-02T06:59:06Z"}}}}'
kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1alpha1
kubeblocks.io/extra-env: '{"mdit-roles":"master,data,ingest,transform","mode":"multi-node"}'
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"apps.kubeblocks.io/v1alpha1","kind":"Cluster","metadata":{"annotations":{"kubeblocks.io/extra-env":"{\"mdit-roles\":\"master,data,ingest,transform\",\"mode\":\"multi-node\"}"},"name":"esearch-cluster","namespace":"default"},"spec":{"clusterDefinitionRef":"elasticsearch","componentSpecs":[{"name":"master","replicas":2,"resources":{"limits":{"cpu":"500m","memory":"2Gi"},"requests":{"cpu":"500m","memory":"2Gi"}},"serviceAccountName":"kb-esearch-cluster","serviceVersion":"7.7.1","volumeClaimTemplates":[{"name":"data","spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"20Gi"}},"storageClassName":null}}]},{"name":"dit","replicas":2,"resources":{"limits":{"cpu":"500m","memory":"2Gi"},"requests":{"cpu":"500m","memory":"2Gi"}},"serviceAccountName":"kb-esearch-cluster","serviceVersion":"7.7.1","volumeClaimTemplates":[{"name":"data","spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"20Gi"}},"storageClassName":null}}]}],"terminationPolicy":"WipeOut","topology":"multi-node"}}
creationTimestamp: "2025-04-02T06:27:23Z"
finalizers:
- cluster.kubeblocks.io/finalizer
generation: 2
labels:
clusterdefinition.kubeblocks.io/name: elasticsearch
clusterversion.kubeblocks.io/name: ""
name: esearch-cluster
namespace: default
resourceVersion: "6023605"
uid: 2e4729e5-d3e7-4229-9171-bea60e26c5d4
spec:
clusterDef: elasticsearch
componentSpecs:
- componentDef: elasticsearch-7
name: master
replicas: 2
resources:
limits:
cpu: 500m
memory: 2Gi
requests:
cpu: 500m
memory: 2Gi
serviceAccountName: kb-esearch-cluster
serviceVersion: 7.7.1
volumeClaimTemplates:
- name: data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- componentDef: elasticsearch-7
name: dit
replicas: 2
resources:
limits:
cpu: 500m
memory: 2Gi
requests:
cpu: 500m
memory: 2Gi
serviceAccountName: kb-esearch-cluster
serviceVersion: 7.7.1
volumeClaimTemplates:
- name: data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
terminationPolicy: WipeOut
topology: multi-node
status:
components:
dit:
message:
InstanceSet/esearch-cluster-dit: '["esearch-cluster-dit-0"]'
phase: Running
master:
message:
InstanceSet/esearch-cluster-master: '["esearch-cluster-master-1"]'
phase: Running
conditions:
- lastTransitionTime: "2025-04-03T02:25:22Z"
message: 'The operator has started the provisioning of Cluster: esearch-cluster'
observedGeneration: 2
reason: PreCheckSucceed
status: "True"
type: ProvisioningStarted
- lastTransitionTime: "2025-04-02T06:27:28Z"
message: Successfully applied for resources
observedGeneration: 2
reason: ApplyResourcesSucceed
status: "True"
type: ApplyResources
- lastTransitionTime: "2025-04-02T06:59:16Z"
message: all pods of components are ready, waiting for the probe detection successful
reason: AllReplicasReady
status: "True"
type: ReplicasReady
- lastTransitionTime: "2025-04-02T06:59:16Z"
message: 'Cluster: esearch-cluster is ready, current phase is Running'
reason: ClusterReady
status: "True"
type: Ready
observedGeneration: 2
phase: Running
kubectl get cmpd -l app.kubernetes.io/name=elasticsearch
NAME SERVICE SERVICE-VERSION STATUS AGE
elasticsearch-7 elasticsearch Available 20h
elasticsearch-7-1.0.0-alpha.0 elasticsearch Available 41m
elasticsearch-8 elasticsearch Available 20h
elasticsearch-8-1.0.0-alpha.0 elasticsearch Available 41m
upgrade-elasticsearch-to-v1.log.txt
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Additional context Add any other context about the problem here.
error: cluster "mysql-cluster" has unknown clusterVersion or componentDefinition, you can replace with accorrding ComponentDefinition with 1.0 api
- create cluster in kb 0.9.4-beta.10
apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
name: mysql-cluster
namespace: default
spec:
terminationPolicy: WipeOut
componentSpecs:
- name: mysql
componentDef: apecloud-mysql
replicas: 3
resources:
requests:
cpu: 100m
memory: 0.5Gi
limits:
cpu: 100m
memory: 0.5Gi
volumeClaimTemplates:
- name: data
spec:
storageClassName:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- install kb 1.0.0-beta.41
- install apecloud-mysql addon 1.0.0-alpha.0
helm list -n kb-system-new
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
kb-addon-apecloud-mysql kb-system-new 1 2025-04-03 10:25:49.249812 +0800 CST deployed apecloud-mysql-1.0.0-alpha.0 8.0.30
- upgrade to v1 see error
echo yes|kbcli cluster upgrade-to-v1 mysql-cluster
error: cluster "mysql-cluster" has unknown clusterVersion or componentDefinition, you can replace with accorrding ComponentDefinition with 1.0 api
after upgrade error cluster yaml
kubectl get cluster mysql-cluster -oyaml
apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
annotations:
kb-increment-converter: '{"spec":{"terminationPolicy":"WipeOut","resources":{"cpu":"0","memory":"0"},"storage":{"size":"0"},"components":{"mysql":{}}},"status":{"components":{"mysql":{"podsReady":true,"podsReadyTime":"2025-04-02T06:33:08Z"}}}}'
kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1alpha1
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"apps.kubeblocks.io/v1alpha1","kind":"Cluster","metadata":{"annotations":{},"name":"mysql-cluster","namespace":"default"},"spec":{"componentSpecs":[{"componentDef":"apecloud-mysql","name":"mysql","replicas":3,"resources":{"limits":{"cpu":"100m","memory":"0.5Gi"},"requests":{"cpu":"100m","memory":"0.5Gi"}},"volumeClaimTemplates":[{"name":"data","spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"20Gi"}},"storageClassName":null}}]}],"terminationPolicy":"WipeOut"}}
creationTimestamp: "2025-04-02T06:27:22Z"
finalizers:
- cluster.kubeblocks.io/finalizer
generation: 2
name: mysql-cluster
namespace: default
resourceVersion: "6023691"
uid: ec2d9b7e-f337-4da2-abdb-47613064bcb3
spec:
componentSpecs:
- componentDef: apecloud-mysql
name: mysql
replicas: 3
resources:
limits:
cpu: 100m
memory: 512Mi
requests:
cpu: 100m
memory: 512Mi
serviceVersion: 8.0.30
volumeClaimTemplates:
- name: data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
terminationPolicy: WipeOut
status:
components:
mysql:
message:
InstanceSet/mysql-cluster-mysql: '["mysql-cluster-mysql-0"]'
phase: Running
conditions:
- lastTransitionTime: "2025-04-03T02:25:26Z"
message: 'The operator has started the provisioning of Cluster: mysql-cluster'
observedGeneration: 2
reason: PreCheckSucceed
status: "True"
type: ProvisioningStarted
- lastTransitionTime: "2025-04-02T06:27:22Z"
message: Successfully applied for resources
observedGeneration: 2
reason: ApplyResourcesSucceed
status: "True"
type: ApplyResources
- lastTransitionTime: "2025-04-02T06:33:08Z"
message: all pods of components are ready, waiting for the probe detection successful
reason: AllReplicasReady
status: "True"
type: ReplicasReady
- lastTransitionTime: "2025-04-02T06:33:08Z"
message: 'Cluster: mysql-cluster is ready, current phase is Running'
reason: ClusterReady
status: "True"
type: Ready
observedGeneration: 2
phase: Running
kubectl get cmpd -l app.kubernetes.io/name=apecloud-mysql
NAME SERVICE SERVICE-VERSION STATUS AGE
apecloud-mysql mysql 8.0.30 Available 20h
apecloud-mysql-1.0.0-alpha.0 mysql 8.0.30 Available 41m
wescale-1.0.0-alpha.0 wescale 0.2.7 Available 41m
wescalecontroller-1.0.0-alpha.0 wescale-ctrl 0.2.7 Available 41m
error: no matched componentDefinition for componentDef tidb-pd-8
- create cluster in kb 0.9.4-beta.10
apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
name: tidb-cluster
namespace: default
spec:
clusterDefinitionRef: tidb
topology: cluster
terminationPolicy: WipeOut
componentSpecs:
- name: tidb
replicas: 1
serviceVersion:
serviceAccountName: kb-tidb-cluster
disableExporter: false
resources:
requests:
cpu: 500m
memory: 2Gi
limits:
cpu: 500m
memory: 2Gi
- name: tikv
replicas: 1
serviceVersion:
serviceAccountName: kb-tidb-cluster
disableExporter: false
resources:
requests:
cpu: 500m
memory: 2Gi
limits:
cpu: 500m
memory: 2Gi
volumeClaimTemplates:
- name: data
spec:
storageClassName:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- name: tidb-pd
replicas: 1
serviceVersion:
serviceAccountName: kb-tidb-cluster
disableExporter: false
resources:
requests:
cpu: 500m
memory: 2Gi
limits:
cpu: 500m
memory: 2Gi
volumeClaimTemplates:
- name: data
spec:
storageClassName:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- install kb 1.0.0-beta.41
- install tidb addon 1.0.0-alpha.0
helm list -n kb-system-new
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
kb-addon-tidb kb-system-new 1 2025-04-03 10:29:02.421594 +0800 CST deployed tidb-1.0.0-alpha.0 v7.1.5
- upgrade to v1 see error
➜ ~ echo yes|kbcli cluster upgrade-to-v1 tidb-cluster
error: no matched componentDefinition for componentDef tidb-pd-8
after upgrade error cluster yaml
kubectl get cluster tidb-cluster -oyaml
apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
annotations:
kb-increment-converter: '{"spec":{"clusterDefinitionRef":"tidb","terminationPolicy":"WipeOut","resources":{"cpu":"0","memory":"0"},"storage":{"size":"0"},"components":{"tidb":{},"tidb-pd":{},"tikv":{}}},"status":{"components":{"tidb":{"podsReady":true,"podsReadyTime":"2025-04-02T06:35:27Z"},"tidb-pd":{"podsReady":true,"podsReadyTime":"2025-04-02T06:32:56Z"},"tikv":{"podsReady":true,"podsReadyTime":"2025-04-02T06:35:05Z"}}}}'
kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1alpha1
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"apps.kubeblocks.io/v1alpha1","kind":"Cluster","metadata":{"annotations":{},"name":"tidb-cluster","namespace":"default"},"spec":{"clusterDefinitionRef":"tidb","componentSpecs":[{"disableExporter":false,"name":"tidb","replicas":1,"resources":{"limits":{"cpu":"500m","memory":"2Gi"},"requests":{"cpu":"500m","memory":"2Gi"}},"serviceAccountName":"kb-tidb-cluster","serviceVersion":null},{"disableExporter":false,"name":"tikv","replicas":1,"resources":{"limits":{"cpu":"500m","memory":"2Gi"},"requests":{"cpu":"500m","memory":"2Gi"}},"serviceAccountName":"kb-tidb-cluster","serviceVersion":null,"volumeClaimTemplates":[{"name":"data","spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"20Gi"}},"storageClassName":null}}]},{"disableExporter":false,"name":"tidb-pd","replicas":1,"resources":{"limits":{"cpu":"500m","memory":"2Gi"},"requests":{"cpu":"500m","memory":"2Gi"}},"serviceAccountName":"kb-tidb-cluster","serviceVersion":null,"volumeClaimTemplates":[{"name":"data","spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"20Gi"}},"storageClassName":null}}]}],"terminationPolicy":"WipeOut","topology":"cluster"}}
creationTimestamp: "2025-04-02T06:27:23Z"
finalizers:
- cluster.kubeblocks.io/finalizer
generation: 2
labels:
clusterdefinition.kubeblocks.io/name: tidb
clusterversion.kubeblocks.io/name: ""
name: tidb-cluster
namespace: default
resourceVersion: "6023651"
uid: a64662b6-d7ca-45ad-bd89-580fd981458f
spec:
clusterDef: tidb
componentSpecs:
- componentDef: tidb-pd-8
disableExporter: false
name: tidb-pd
replicas: 1
resources:
limits:
cpu: 500m
memory: 2Gi
requests:
cpu: 500m
memory: 2Gi
serviceAccountName: kb-tidb-cluster
serviceVersion: 8.4.0
volumeClaimTemplates:
- name: data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- componentDef: tikv-8
disableExporter: false
name: tikv
replicas: 1
resources:
limits:
cpu: 500m
memory: 2Gi
requests:
cpu: 500m
memory: 2Gi
serviceAccountName: kb-tidb-cluster
serviceVersion: 8.4.0
volumeClaimTemplates:
- name: data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- componentDef: tidb-8
disableExporter: false
name: tidb
replicas: 1
resources:
limits:
cpu: 500m
memory: 2Gi
requests:
cpu: 500m
memory: 2Gi
serviceAccountName: kb-tidb-cluster
serviceVersion: 8.4.0
terminationPolicy: WipeOut
topology: cluster
status:
components:
tidb:
phase: Running
tidb-pd:
phase: Running
tikv:
message:
InstanceSet/tidb-cluster-tikv: '["tidb-cluster-tikv-0"]'
phase: Running
conditions:
- lastTransitionTime: "2025-04-03T02:25:25Z"
message: 'The operator has started the provisioning of Cluster: tidb-cluster'
observedGeneration: 2
reason: PreCheckSucceed
status: "True"
type: ProvisioningStarted
- lastTransitionTime: "2025-04-02T06:27:30Z"
message: Successfully applied for resources
observedGeneration: 2
reason: ApplyResourcesSucceed
status: "True"
type: ApplyResources
- lastTransitionTime: "2025-04-02T06:35:27Z"
message: all pods of components are ready, waiting for the probe detection successful
reason: AllReplicasReady
status: "True"
type: ReplicasReady
- lastTransitionTime: "2025-04-02T06:35:27Z"
message: 'Cluster: tidb-cluster is ready, current phase is Running'
reason: ClusterReady
status: "True"
type: Ready
observedGeneration: 2
phase: Running
kubectl get cmpd -l app.kubernetes.io/name=tidb
NAME SERVICE SERVICE-VERSION STATUS AGE
tidb-7 MySQL Available 20h
tidb-7-1.0.0-alpha.0 MySQL Available 38m
tidb-8 MySQL Available 20h
tidb-pd-7 Available 20h
tidb-pd-7-1.0.0-alpha.0 Available 38m
tidb-pd-8 Available 20h
tikv-7 Available 20h
tikv-7-1.0.0-alpha.0 Available 38m
tikv-8 Available 20h
tidb-8 missing in 1.0
has been fixed
- elasticsearch
echo yes|kbcli cluster upgrade-to-v1 esearch-cluster
┌────────────────────────────────────────────────────────────────────────────────────────────────┐ ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
│apiVersion: apps.kubeblocks.io/v1alpha1 │ │apiVersion: apps.kubeblocks.io/v1 │
│kind: Cluster │ │kind: Cluster │
│metadata: │ │metadata: │
│ annotations: │ │ annotations: │
│ kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1alpha1 │ │ kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1 │
│ kubeblocks.io/extra-env: '{"mdit-roles":"master,data,ingest,transform","mode":"multi-node"}'│ │ kubeblocks.io/extra-env: '{"mdit-roles":"master,data,ingest,transform","mode":"multi-node"}'│
│ creationTimestamp: "2025-04-28T07:23:40Z" │ │ creationTimestamp: "2025-04-28T07:23:40Z" │
│ finalizers: │ │ finalizers: │
│ - cluster.kubeblocks.io/finalizer │ │ - cluster.kubeblocks.io/finalizer │
│ generation: 2 │ │ generation: 2 │
│ labels: │ │ labels: │
│ clusterdefinition.kubeblocks.io/name: elasticsearch │ │ clusterdefinition.kubeblocks.io/name: elasticsearch │
│ clusterversion.kubeblocks.io/name: "" │ │ clusterversion.kubeblocks.io/name: "" │
│ name: esearch-cluster │ │ name: esearch-cluster │
│ namespace: default │ │ namespace: default │
│ resourceVersion: "36366" │ │ resourceVersion: "36366" │
│ uid: c7c24a54-330b-4061-8e05-6735a69cd8d5 │ │ uid: c7c24a54-330b-4061-8e05-6735a69cd8d5 │
│spec: │ │spec: │
│ clusterDefinitionRef: elasticsearch │ │ clusterDef: elasticsearch │
│ componentSpecs: │ │ componentSpecs: │
│ - componentDef: elasticsearch-7 │ │ - componentDef: elasticsearch-7-1.0.0-alpha.0 │
│ name: master │ │ name: master │
│ replicas: 2 │ │ replicas: 2 │
│ resources: │ │ resources: │
│ limits: │ │ limits: │
│ cpu: 500m │ │ cpu: 500m │
│ memory: 2Gi │ │ memory: 2Gi │
│ requests: │ │ requests: │
│ cpu: 500m │ │ cpu: 500m │
│ memory: 2Gi │ │ memory: 2Gi │
│ serviceAccountName: kb-esearch-cluster │ │ serviceVersion: 7.7.1 │
│ serviceVersion: 7.7.1 │ │ volumeClaimTemplates: │
│ volumeClaimTemplates: │ │ - name: data │
│ - name: data │ │ spec: │
│ spec: │ │ accessModes: │
│ accessModes: │ │ - ReadWriteOnce │
│ - ReadWriteOnce │ │ resources: │
│ resources: │ │ requests: │
│ requests: │ │ storage: 20Gi │
│ storage: 20Gi │ │ - componentDef: elasticsearch-7-1.0.0-alpha.0 │
│ - componentDef: elasticsearch-7 │ │ name: dit │
│ name: dit │ │ replicas: 2 │
│ replicas: 2 │ │ resources: │
│ resources: │ │ limits: │
│ limits: │ │ cpu: 500m │
│ cpu: 500m │ │ memory: 2Gi │
│ memory: 2Gi │ │ requests: │
│ requests: │ │ cpu: 500m │
│ cpu: 500m │ │ memory: 2Gi │
│ memory: 2Gi │ │ serviceVersion: 7.7.1 │
│ serviceAccountName: kb-esearch-cluster │ │ volumeClaimTemplates: │
│ serviceVersion: 7.7.1 │ │ - name: data │
│ volumeClaimTemplates: │ │ spec: │
│ - name: data │ │ accessModes: │
│ spec: │ │ - ReadWriteOnce │
│ accessModes: │ │ resources: │
│ - ReadWriteOnce │ │ requests: │
│ resources: │ │ storage: 20Gi │
│ requests: │ │ terminationPolicy: WipeOut │
│ storage: 20Gi │ │ topology: multi-node │
│ resources: │ │status: {} │
│ cpu: "0" │ │ │
│ memory: "0" │ └────────────────────────────────────────────────────────────────────────────────────────────────┘
│ storage: │
│ size: "0" │
│ terminationPolicy: WipeOut │
│ topology: multi-node │
│status: {} │
│ │
└────────────────────────────────────────────────────────────────────────────────────────────────┘
Cluster esearch-cluster will be converted to v1 with output as yaml.
Please type 'Yes/yes' to confirm your operation: yes
esearch-cluster-dit-http
esearch-cluster-master-http
Cluster esearch-cluster has converted successfully, you can view the spec:
kubectl get clusters.apps.kubeblocks.io esearch-cluster -n default -oyaml
kubectl get cluster esearch-cluster
NAME CLUSTER-DEFINITION TERMINATION-POLICY STATUS AGE
esearch-cluster elasticsearch WipeOut Running 77m
➜ ~
➜ ~ kubectl get pod -l app.kubernetes.io/instance=esearch-cluster
NAME READY STATUS RESTARTS AGE
esearch-cluster-dit-0 3/3 Running 0 19m
esearch-cluster-dit-1 3/3 Running 0 22m
esearch-cluster-master-0 3/3 Running 0 19m
esearch-cluster-master-1 3/3 Running 0 22m
kubectl get clusters.apps.kubeblocks.io esearch-cluster -n default -oyaml
apiVersion: apps.kubeblocks.io/v1
kind: Cluster
metadata:
annotations:
kubeblocks.io/crd-api-version: apps.kubeblocks.io/v1
kubeblocks.io/extra-env: '{"mdit-roles":"master,data,ingest,transform","mode":"multi-node"}'
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"apps.kubeblocks.io/v1alpha1","kind":"Cluster","metadata":{"annotations":{"kubeblocks.io/extra-env":"{\"mdit-roles\":\"master,data,ingest,transform\",\"mode\":\"multi-node\"}"},"name":"esearch-cluster","namespace":"default"},"spec":{"clusterDefinitionRef":"elasticsearch","componentSpecs":[{"name":"master","replicas":2,"resources":{"limits":{"cpu":"500m","memory":"2Gi"},"requests":{"cpu":"500m","memory":"2Gi"}},"serviceAccountName":"kb-esearch-cluster","serviceVersion":"7.7.1","volumeClaimTemplates":[{"name":"data","spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"20Gi"}},"storageClassName":null}}]},{"name":"dit","replicas":2,"resources":{"limits":{"cpu":"500m","memory":"2Gi"},"requests":{"cpu":"500m","memory":"2Gi"}},"serviceAccountName":"kb-esearch-cluster","serviceVersion":"7.7.1","volumeClaimTemplates":[{"name":"data","spec":{"accessModes":["ReadWriteOnce"],"resources":{"requests":{"storage":"20Gi"}},"storageClassName":null}}]}],"terminationPolicy":"WipeOut","topology":"multi-node"}}
creationTimestamp: "2025-04-28T07:23:40Z"
finalizers:
- cluster.kubeblocks.io/finalizer
generation: 3
labels:
clusterdefinition.kubeblocks.io/name: elasticsearch
clusterversion.kubeblocks.io/name: ""
name: esearch-cluster
namespace: default
resourceVersion: "61723"
uid: c7c24a54-330b-4061-8e05-6735a69cd8d5
spec:
clusterDef: elasticsearch
componentSpecs:
- componentDef: elasticsearch-7-1.0.0-alpha.0
name: master
replicas: 2
resources:
limits:
cpu: 500m
memory: 2Gi
requests:
cpu: 500m
memory: 2Gi
serviceVersion: 7.7.1
volumeClaimTemplates:
- name: data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
- componentDef: elasticsearch-7-1.0.0-alpha.0
name: dit
replicas: 2
resources:
limits:
cpu: 500m
memory: 2Gi
requests:
cpu: 500m
memory: 2Gi
serviceVersion: 7.7.1
volumeClaimTemplates:
- name: data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
terminationPolicy: WipeOut
topology: multi-node
status:
components:
dit:
phase: Running
master:
phase: Running
conditions:
- lastTransitionTime: "2025-04-28T08:07:37Z"
message: 'The operator has started the provisioning of Cluster: esearch-cluster'
observedGeneration: 3
reason: PreCheckSucceed
status: "True"
type: ProvisioningStarted
- lastTransitionTime: "2025-04-28T07:23:45Z"
message: Successfully applied for resources
observedGeneration: 3
reason: ApplyResourcesSucceed
status: "True"
type: ApplyResources
- lastTransitionTime: "2025-04-28T07:27:58Z"
message: all pods of components are ready, waiting for the probe detection successful
reason: AllReplicasReady
status: "True"
type: ReplicasReady
- lastTransitionTime: "2025-04-28T07:27:58Z"
message: cluster esearch-cluster is ready
reason: ClusterReady
status: "True"
type: Ready
observedGeneration: 3
phase: Running