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.26.6-gke.1700 KubeBlocks: 0.8.0 kbcli: 0.8.0
To Reproduce Steps to reproduce the behavior:
apiVersion: apps.kubeblocks.io/v1alpha1 kind: Cluster metadata: name: zkeeper-pbmwtr namespace: default spec: clusterDefinitionRef: zookeeper clusterVersionRef: zookeeper-3.7.2 terminationPolicy: DoNotTerminate componentSpecs: - name: zookeeper componentDefRef: zookeeper 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: 1Gi - name: data-log spec: storageClassName: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi
kbcli cluster connect zkeeper-pbmwtr Connect to instance zkeeper-pbmwtr-zookeeper-0: out of zkeeper-pbmwtr-zookeeper-0, zkeeper-pbmwtr-zookeeper-1 error: unsupported engine type: zookeeper
Expected behavior kbcli connect zookeeper cluster success
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:
zookeeper connect commands are not supported in kubeblocks.lorry.
kubeblocks.lorry
Sorry, something went wrong.
1aal
No branches or pull requests
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
kbcli connect zookeeper cluster success
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: