x509: certificate signed by unknown authority
A TLS client received a certificate it can’t chain to any CA it trusts. Where you see it tells you which trust store is missing what.
Where it happens, and what’s missing
Section titled “Where it happens, and what’s missing”| Where | Missing trust | Fix |
|---|---|---|
kubectl |
Your kubeconfig’s certificate-authority-data doesn’t match the API server’s CA, often after a cluster rebuild or through a TLS-inspecting corporate proxy |
Get a fresh kubeconfig; exclude the API server from TLS inspection |
| Image pull from a private registry | The node’s container runtime doesn’t trust the registry’s CA | Install the CA on nodes (for containerd, under its registry certs directory) or use a publicly trusted certificate |
| Admission webhook calls | The webhook configuration’s caBundle doesn’t match the certificate the webhook serves |
Let cert-manager’s CA injector maintain caBundle, or update it when the certificate rotates |
| App to app inside the cluster | The calling container’s image doesn’t include your internal CA | Add the CA to the image’s trust store or mount it |
Diagnose
Section titled “Diagnose”Look at the certificate actually served:
openssl s_client -connect <host>:<port> -servername <host> </dev/null 2>/dev/null | openssl x509 -noout -issuer -subject -datesIf the issuer is your company’s proxy rather than the expected CA, the connection is being intercepted.
Don’t fix it with --insecure-skip-tls-verify or an insecure registry setting outside a throwaway lab. In regulated environments that’s an audit finding, and it removes the protection TLS exists for.