search

kubernetes / minikube

Run Kubernetes locally
https://minikube.sigs.k8s.io/
Apache License 2.0
29.42k stars 4.88k forks source link

webhook dns #18996

Closed YZF-Myself closed 5 days ago

YZF-Myself commented 5 months ago

What Happened?

I refer to: https://didil.medium.com/autobucket-operator-7e77eca95fcc https://cloud.tencent.com/developer/article/2363996

environment： minikube version: v1.31.2 gcr.io/k8s-minikube/kicbase v0.0.43 619d67e74933 6 weeks ago 1.26GB

start： minikube start --kubernetes-version=v1.23.0 --force --driver=docker --bootstrapper=kubeadm --extra-config=scheduler.address=0.0.0.0 --extra-config=controller-manager.address=0.0.0.0

question:

kubectl run busybox-1 --image=busybox --restart=Never -l=app=busybox,hello=true -- sleep 3600

Error from server (InternalError): Internal error occurred: failed calling webhook "hello-webhook.leclouddev.com": failed to call webhook: Post "https://webhook-svc.mutating-webhook.svc:443/mutate?timeout=10s": dial tcp 10.100.140.127:443: connect: connection refused

Attach the log file

kubectl logs -n kube-system -l k8s-app=kube-dns

[INFO] plugin/ready: Still waiting on: "kubernetes" .:53 [INFO] plugin/reload: Running configuration MD5 = efb55b6c40fa64314ecca5d48a313e92 CoreDNS-1.8.6 linux/amd64, go1.17.1, 13a9191 [INFO] 127.0.0.1:54512 - 21808 "HINFO IN 7193728981579617635.3349875443182598247. udp 57 false 512" NXDOMAIN qr,rd,ra 132 0.554889763s

./generate_certificate.sh --service webhook-svc --webhook hello-webhook.leclouddev.com --secret hello-tls-secret --namespace mutating-webhookcreating certs in tmpdir /tmp/tmp.xRsa9GCOOB /CN=webhook-svc.mutating-webhook.svc Generating RSA private key, 2048 bit long modulus (2 primes) ........+++++ ...............................................................................................................................................................................+++++ e is 65537 (0x010001) Error from server (NotFound): certificatesigningrequests.certificates.k8s.io "webhook-svc.mutating-webhook" not found certificatesigningrequest.certificates.k8s.io/webhook-svc.mutating-webhook created NAME AGE SIGNERNAME REQUESTOR REQUESTEDDURATION CONDITION webhook-svc.mutating-webhook 0s kubernetes.io/kubelet-serving minikube-user Pending CertificateSigningRequest create succsee certificatesigningrequest.certificates.k8s.io/webhook-svc.mutating-webhook approved webhook-svc.mutating-webhook certificate approve W0531 10:35:19.953593 61585 helpers.go:692] --dry-run is deprecated and can be replaced with --dry-run=client. secret/hello-tls-secret created INFO: Trying to patch webhook adding the caBundle. mutatingwebhookconfiguration.admissionregistration.k8s.io/hello-webhook.leclouddev.com patched

Operating System

None

Driver

None

YZF-Myself commented 5 months ago

Minikube docker starts multiple nodes, and the network between multiple nodes is not connected.

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 5 days ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 5 days ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/minikube/issues/18996#issuecomment-2440584926): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.