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

Error from server (InternalError): Internal error occurred: failed calling webhook "webhook.cert-manager.io" #7312

Open
tuanhuynhvn opened this issue Sep 30, 2024 · 1 comment
Labels
priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@tuanhuynhvn
Copy link

I am setting up a k8s cluster in 2 ec2 instances.
I install cert-manager: kubectl apply -f https:/cert-manager/cert-manager/releases/download/v1.15.3/cert-manager.yaml

kubectl get node

NAME               STATUS   ROLES           AGE   VERSION
ip-172-31-31-197   Ready    <none>          39m   v1.31.1
ip-172-31-31-79    Ready    control-plane   41m   v1.31.1

kubectl get pod --all-namespaces

NAMESPACE      NAME                                       READY   STATUS             RESTARTS        AGE
cert-manager   cert-manager-7fbbc65b49-mj848              1/1     Running            0               30m
cert-manager   cert-manager-cainjector-6664fc84f6-v7w7q   1/1     Running            0               30m
cert-manager   cert-manager-webhook-59598898fd-cfvhp      1/1     Running            0               30m
kube-flannel   kube-flannel-ds-5qtfz                      1/1     Running            0               37m
kube-flannel   kube-flannel-ds-k8m7x                      1/1     Running            0               39m
kube-system    coredns-7c65d6cfc9-5qq2l                   1/1     Running            0               39m
kube-system    coredns-7c65d6cfc9-69t5n                   1/1     Running            0               39m
kube-system    etcd-ip-172-31-31-79                       1/1     Running            0               39m
kube-system    kube-apiserver-ip-172-31-31-79             1/1     Running            0               39m
kube-system    kube-controller-manager-ip-172-31-31-79    1/1     Running            0               39m
kube-system    kube-proxy-4svnx                           1/1     Running            9 (6m39s ago)   37m
kube-system    kube-proxy-nbldj                           0/1     CrashLoopBackOff   10 (98s ago)    39m
kube-system    kube-scheduler-ip-172-31-31-79             1/1     Running            0               39m

cmctl check api
Error from server (InternalError): Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/validate?timeout=30s": context deadline exceeded

kubectl apply -f test-resources.yaml

namespace/cert-manager-test created
Error from server (InternalError): error when creating "test-resources.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/validate?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Error from server (InternalError): error when creating "test-resources.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/validate?timeout=30s": context deadline exceeded
@wallrj
Copy link
Member

wallrj commented Oct 4, 2024

Might be problem with your kube-proxy. I see the following in your kubectl get pods output

kube-system    kube-proxy-nbldj                           0/1     CrashLoopBackOff   10 (98s ago)    39m

@ThatsMrTalbot ThatsMrTalbot added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

3 participants