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

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 · 3 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.
Milestone

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

# 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 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
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
Status: Planned In Release 1.10
Development

No branches or pull requests

3 participants