By Ilythae
I’ve been trying to deploy and configure Istio within a Kubernetes cluster (both with and without Helm), but there seems to be an issue when it comes to the webhooks it uses. The sidecar injector and the config validation webhooks return with a failed calling admission webhook: connection refused error, despite all pods and services running correctly.
I’ve seen mentions of required kube-apiserver plugins (MutatingAdmissionWebhook and ValidatingAdmissionWebhook) for these webhooks to function - are these included with the Kubernetes clusters we create? Or is there something additional in DigitalOcean that is blocking these requests? Does anyone else have experience with this issue?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi friend, I checked with our internal DOKS team and at a high level they note that the admission webhook permissions are enabled by default. They’d like to take a look at your cluster directly, so in order to kick that off can you please log a ticket (as your control panel user) on https://cloudsupport.digitalocean.com
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.