You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -212,7 +212,7 @@ Unable to connect to the server: x509: certificate signed by unknown authority (
212
212
213
213
By default, kubeadm configures a kubelet with automatic rotation of client certificates by using the `/var/lib/kubelet/pki/kubelet-client-current.pem` symlink specified in `/etc/kubernetes/kubelet.conf`.
214
214
If this rotation process fails you might see errors such as `x509: certificate has expired or is not yet valid`
215
-
in kube-apserver logs. To fix the issue you must follow these steps:
215
+
in kube-apiserver logs. To fix the issue you must follow these steps:
216
216
217
217
1. Backup and delete `/etc/kubernetes/kubelet.conf` and `/var/lib/kubelet/pki/kubelet-client*` from the failed node.
218
218
1. From a working control plane node in the cluster that has `/etc/kubernetes/pki/ca.key` execute
0 commit comments