Skip to content
New issue

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

[BUG]connection refused error occurred when using kbcli command to create dmdb cluster #8091

Closed
tianyue86 opened this issue Sep 5, 2024 · 2 comments · Fixed by #8099
Closed
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@tianyue86
Copy link

Environment info

kbcli version
Kubernetes: v1.29.7-gke.1104000
KubeBlocks: 0.9.1-beta.20
kbcli: 0.9.1-beta.9

To Reproduce
Steps to reproduce the behavior:

  1. create dmdb cluster using kbcli command
    kbcli cluster create dmdb-zirgpm --termination-policy=DoNotTerminate --cluster-definition=dmdb --enable-all-logs=false --cluster-version=dmdb-0.1.0 --set cpu=100m,memory=0.5Gi,replicas=1,storage=1Gi --namespace default

  2. See error
    Error from server (InternalError): Internal error occurred: failed calling webhook "vcluster.kb.io": failed to call webhook: Post "https://kubeblocks.kb-system.svc:9443/validate-apps-kubeblocks-io-v1alpha1-cluster?timeout=10s": dial tcp 10.8.4.4:9443: connect: connection refused

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.

@tianyue86 tianyue86 added the kind/bug Something isn't working label Sep 5, 2024
@tianyue86 tianyue86 added this to the Release 0.9.1 milestone Sep 5, 2024
@ldming ldming assigned sophon-zt and unassigned sophon-zt Sep 5, 2024
@sophon-zt
Copy link
Contributor

img_v3_02ee_ce6a1cc8-80d4-4b7d-b49f-7bf97386513g

@ldming
Copy link
Collaborator

ldming commented Sep 5, 2024

If the webhook is enabled, maybe a wrong service is selected, we should use different label for KubeBlocks and DataProtection pod.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants