<p>I'm trying to understand the security implications for using self-signed certificates for a Kubernetes validating webhook.</p>
<p>If I'm understanding correctly, the certificate is simply used to be able to serve the validating webhook server over https.  When the Kubernetes api-server receives a request that matches the configuration for a validating webhook, it'll first check with the validating webhook server over https.  If your validating webhook server lives on the Kubernetes cluster (is not external) then this traffic is all internal to a Kubernetes cluster.  If this is the case is it problematic that the cert is self-signed?</p>

<blockquote>
<p>If I'm understanding correctly, the certificate is simply used to be
able to serve the validating webhook server over https.</p>
</blockquote>
<p>Basically yes.</p>
<blockquote>
<p>If your validating webhook server lives on the Kubernetes cluster (is
not external) then this traffic is all internal to a Kubernetes
cluster. If this is the case is it problematic that the cert is
self-signed?</p>
</blockquote>
<p>If the issuing process is handled properly and in secure manner, self-signed certs shouldn't be a problem at all. Compare with <a href="https://gist.github.com/tirumaraiselvan/b7eb1831d25dd9d59a785c11bd46c84b" rel="nofollow noreferrer">this</a> example.</p>
