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.

Sign up for GitHub

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

Jump to bottom

operator: dial tcp: lookup karmada-webhook.karmada-system.svc on x.x.x.x: no such host #4893

Open
zhzhuang-zju opened this issue Apr 30, 2024 · 8 comments · May be fixed by #6079
Open

operator: dial tcp: lookup karmada-webhook.karmada-system.svc on x.x.x.x: no such host #4893

zhzhuang-zju opened this issue Apr 30, 2024 · 8 comments · May be fixed by #6079
Assignees
@calvin0327 @zhzhuang-zju
Labels
kind/bug Categorizes issue or PR as related to a bug.
Milestone
v1.13

Comments

@zhzhuang-zju
Copy link
Contributor

What happened:
when deploying karmada instance by operator，karmada-apiserver will report dial tcp: lookup karmada-webhook.karmada-system.svc on x.x.x.x: no such host error if the namespace of karmada instance is not karmada-system.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Karmada version: v1.9.0
  • kubectl-karmada or karmadactl version (the result of kubectl-karmada version or karmadactl version):
  • Others:
@zhzhuang-zju zhzhuang-zju added the kind/bug Categorizes issue or PR as related to a bug. label Apr 30, 2024
@zhzhuang-zju
Copy link
Contributor Author

karmada/charts/karmada/_crds/patches/webhook_in_resourcebindings.yaml

Lines 1 to 14 in 211351b

# The following patch enables conversion webhook for CRD
# CRD conversion requires k8s 1.13 or later.
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
name: resourcebindings.work.karmada.io
spec:
conversion:
strategy: Webhook
webhook:
clientConfig:
url: https://karmada-webhook.karmada-system.svc:443/convert
caBundle: {{caBundle}}
conversionReviewVersions: ["v1"]

The url is hardcoded and actually needs to be entered via a variable.

@RainbowMango RainbowMango moved this to Planned In Release 1.10 in Karmada Overall Backlog Apr 30, 2024
@RainbowMango RainbowMango added this to the v1.10 milestone Apr 30, 2024
@RainbowMango
Copy link
Member

cc @calvin0327 to confirm
I remember it's the basic use case that enables installation in customized namespace.

@calvin0327
Copy link

/assign

@RainbowMango RainbowMango modified the milestones: v1.10, v1.11 May 29, 2024
@RainbowMango RainbowMango moved this from Planned In Release 1.10 to Triaging in Karmada Overall Backlog Jun 4, 2024
@RainbowMango
Copy link
Member

ping @calvin0327 @zhzhuang-zju

@zhzhuang-zju
Copy link
Contributor Author

ping @calvin0327 @zhzhuang-zju

I will double-check to see if this issue exists.

@RainbowMango RainbowMango modified the milestones: v1.11, v1.12 Aug 31, 2024
@zhzhuang-zju
Copy link
Contributor Author

After re-verification, error logs were still found in the karmada-apiserver

$ kubectl get svc -A
NAMESPACE        NAME                                TYPE           CLUSTER-IP   EXTERNAL-IP                                  PORT(S)   AGE
default          kubernetes                          ClusterIP      10.96.0.1    <none>                                       443/TCP   11d
karmada-system   karmada-demo-aggregated-apiserver   ExternalName   <none>       karmada-demo-aggregated-apiserver.test.svc   <none>    11d
karmada-system   karmada-demo-metrics-adapter        ExternalName   <none>       karmada-demo-metrics-adapter.test.svc        <none>    11d
karmada-system   karmada-demo-search                 ExternalName   <none>       karmada-demo-search.test.svc                 <none>    11d
$ kubectl logs -f --namespace test karmada-demo-apiserver-69794b89d5-9lcvv
W1112 09:24:01.326687       1 reflector.go:547] storage/cacher.go:/work.karmada.io/resourcebindings: failed to list work.karmada.io/v1alpha1, Kind=ResourceBinding: conversion webhook for work.karmada.io/v1alpha2, Kind=ResourceBinding failed: Post "https://karmada-webhook.karmada-system.svc:443/convert?timeout=30s": dial tcp: lookup karmada-webhook.karmada-system.svc on 10.96.0.10:53: no such host
E1112 09:24:01.326699       1 cacher.go:476] cacher (resourcebindings.work.karmada.io): unexpected ListAndWatch error: failed to list work.karmada.io/v1alpha1, Kind=ResourceBinding: conversion webhook for work.karmada.io/v1alpha2, Kind=ResourceBinding failed: Post "https://karmada-webhook.karmada-system.svc:443/convert?timeout=30s": dial tcp: lookup karmada-webhook.karmada-system.svc on 10.96.0.10:53: no such host; reinitializing...

@zhzhuang-zju
Copy link
Contributor Author

cc @RainbowMango @calvin0327

@RainbowMango RainbowMango modified the milestones: v1.12, v1.13 Nov 28, 2024
@zhzhuang-zju zhzhuang-zju linked a pull request Jan 23, 2025 that will close this issue
Open
@zhzhuang-zju
Copy link
Contributor Author

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@calvin0327 calvin0327

@zhzhuang-zju zhzhuang-zju

Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
Karmada Overall Backlog
Status: Triaging
Milestone
v1.13
Development

Successfully merging a pull request may close this issue.

karmada-webhook: fix the no such host error zhzhuang-zju/karmada
3 participants
@RainbowMango @calvin0327 @zhzhuang-zju