-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Internal error occurred: failed calling webhook "webhook.serving.knative.dev": failed to call webhook: Post "https://webhook.knative-serving.svc:443/defaulting?timeout=10s": context deadline exceeded #13045
Comments
We're having the same problem in a Kourier Knative deployment right now. This deployment has been stable for quite a while. |
This issue is stale because it has been open for 90 days with no |
I have had this just now as well and it surely wasn't the first time. Twice actually. Kourier with Knative Serving.
/remove-lifecycle stale |
I'm getting this issue on GKE autopilot as well. |
Same issue here. I installed it on K8s 1.22 using Knative Operator and I get the same error trying to deploy a Service. |
Hey folks - can you post a gist link with logs. Generally we've seen errors like this when the API server is under-provisioned. If you have a way to reproduce this that would be even better. |
Thanks for responding, @dprotaso. That's also what I expected, but unfortunately I do not manage the deployment of the API server. We use Scaleway's managed control plane offering named Kapsule. Unfortunately no way to reproduce consistently. Will get back to you with logs. |
Thanks for your reply @dprotaso . In my case, I don't have access to API as this is an EKS instance with one t3.medium worker node. Here you can find the logs. |
I think I've found the problem. My instance of EKS was deployed with the prefix delegation enabled on the CNI plugin (I did this to have capacity for 110 pods per node instead of 17) using this TF module as example. Using an EKS without prefix delegation Knative is working as expected. |
We run our clusters on GKE. The webhook call is made from the apiserver. The webhook pod listens on 8443 whilst the service listens on 443. When making the webhook call the GKE apiserver tries to hit the webhook pod on 8443. Only ports 443 and 10250 are open between the apiserver and the GKE nodes. I solved this issue by creating a firewall rule that allowed the apiserver to talk to the nodes over 8443. It took me a while to figure this out. If you are seeing |
check proxy |
Ask your question here:
**there is an e rror when i create knative service **
kubernetes: v1.23.7
Knative Install type : yaml https://knative.dev/docs/install/yaml-install/serving/install-serving-with-yaml/
network layer :istio
----------------env------------------
----------------kube-api logs-----------------------
-----------------webhook logs---------------------
The text was updated successfully, but these errors were encountered: