We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
kbcli version Kubernetes: v1.28.3-vke.17 KubeBlocks: 0.9.3-beta.7 kbcli: 0.9.2
To Reproduce Steps to reproduce the behavior:
apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: asmysql-bbarka namespace: default spec: terminationPolicy: Halt componentSpecs: - name: mysql componentDef: mysql-8.0 serviceVersion: 8.0.30 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: 10Gi
kbcli cluster backup asmysql-bbarka --method xtrabackup --namespace default error: not found any backup policy for cluster "asmysql-bbarka" [Error] xtrabackup backup command execute error
kubectl get backuppolicy -l app.kubernetes.io/instance=asmysql-bbarka No resources found in default namespace.
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):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
kubectl describe cluster asmysql-bbarka Name: asmysql-bbarka Namespace: default Labels: <none> Annotations: <none> API Version: apps.kubeblocks.io/v1alpha1 Kind: Cluster Metadata: Creation Timestamp: 2024-12-12T03:35:10Z Finalizers: cluster.kubeblocks.io/finalizer Generation: 1 Resource Version: 11185520 UID: a8d3983f-648c-46ca-a38c-dc9ecec21c1f Spec: Component Specs: Component Def: mysql-8.0 Name: mysql Replicas: 2 Resources: Limits: Cpu: 100m Memory: 0.5Gi Requests: Cpu: 100m Memory: 0.5Gi Service Version: 8.0.30 Volume Claim Templates: Name: data Spec: Access Modes: ReadWriteOnce Resources: Requests: Storage: 10Gi Termination Policy: Halt Status: Components: Mysql: Phase: Creating Pods Ready: false Conditions: Last Transition Time: 2024-12-12T03:35:10Z Message: The operator has started the provisioning of Cluster: asmysql-bbarka Observed Generation: 1 Reason: PreCheckSucceed Status: True Type: ProvisioningStarted Last Transition Time: 2024-12-12T03:35:10Z Message: Successfully applied for resources Observed Generation: 1 Reason: ApplyResourcesSucceed Status: True Type: ApplyResources Last Transition Time: 2024-12-12T03:35:11Z Message: pods are not ready in Components: [mysql], refer to related component message in Cluster.status.components Reason: ReplicasNotReady Status: False Type: ReplicasReady Last Transition Time: 2024-12-12T03:35:11Z Message: pods are unavailable in Components: [mysql], refer to related component message in Cluster.status.components Reason: ComponentsNotReady Status: False Type: Ready Observed Generation: 1 Phase: Creating Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal PreCheckSucceed 7s cluster-controller The operator has started the provisioning of Cluster: asmysql-bbarka Normal ApplyResourcesSucceed 7s cluster-controller Successfully applied for resources Normal ComponentPhaseTransition 7s cluster-controller component is Creating
Sorry, something went wrong.
fixed at apecloud/kubeblocks-addons#1310
wangyelei
No branches or pull requests
Describe the bug
To Reproduce
Steps to reproduce the behavior:
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):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: