In the vSphere GUI there is a Supervisor Cluster upgrade in progress that is stuck with a "Component Configuration error:"
failed to verify certificate: x509: certificate signed by unknown authority Component upgrade failed.
While connected to the Supervisor cluster context, the following symptoms are observed:
kubectl get nodes -A
kubectl get pods -A | grep -v Run
kubectl get certificates -A | grep <certificate called out in error message>
kubectl describe certificate -n <namespace> <certificate name>
kubectl get pods -A | grep kube-apiserver
kubectl logs -n kube-system <kube-apiserver pod name>
kubectl logs -n kube-system <kube-apiserver pod name>
"x509: certificate signed by unknown authority"vSphere with Tanzu 7.0
vSphere with Tanzu 8.0
The cert-manager pod in the Supervisor Cluster ensures secure and automated TLS certificate lifecycle management for various internal services, webhooks, and APIs. This enables zero-touch secure communication within the cluster and its extensions.
If cert-manager certificate validation stops working, a restart might be needed after confirming the certificates are valid.
Perform a rolling restart of the cert-manager deployments
kubectl get deployment -A | grep cert
vmware-system-cert-manager cert-manager
vmware-system-cert-manager cert-manager-cainjector
vmware-system-cert-manager cert-manager-webhook
kubectl rollout restart deployment -n vmware-system-cert-manager cert-manager
kubectl rollout restart deployment -n vmware-system-cert-manager cert-manager-cainjector
kubectl rollout restart deployment -n vmware-system-cert-manager cert-manager-webhook