Unable to connect to the server: x509: certificate has expired or is not yet valid: current time 2024-03-04T14:26:31+08:00 is after 2024-02-27T08:36:50Z
[root@ALSHBSITL00061 kubernetes]# kubeadm certs check-expiration [check-expiration] Reading configuration from the cluster... [check-expiration] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml' [check-expiration] Error reading configuration from the Cluster. Falling back to default configuration
CERTIFICATE EXPIRES RESIDUAL TIME CERTIFICATE AUTHORITY EXTERNALLY MANAGED admin.conf Feb 27, 2024 08:36 UTC <invalid> ca no apiserver Feb 27, 2024 08:36 UTC <invalid> ca no apiserver-etcd-client Feb 27, 2024 08:36 UTC <invalid> etcd-ca no apiserver-kubelet-client Feb 27, 2024 08:36 UTC <invalid> ca no controller-manager.conf Feb 27, 2024 08:36 UTC <invalid> ca no etcd-healthcheck-client Feb 27, 2024 08:36 UTC <invalid> etcd-ca no etcd-peer Feb 27, 2024 08:36 UTC <invalid> etcd-ca no etcd-server Feb 27, 2024 08:36 UTC <invalid> etcd-ca no front-proxy-client Feb 27, 2024 08:36 UTC <invalid> front-proxy-ca no scheduler.conf Feb 27, 2024 08:36 UTC <invalid> ca no
CERTIFICATE AUTHORITY EXPIRES RESIDUAL TIME EXTERNALLY MANAGED ca Feb 24, 2033 08:36 UTC 8y no etcd-ca Feb 24, 2033 08:36 UTC 8y no front-proxy-ca Feb 24, 2033 08:36 UTC 8y no
执行续期操作
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
[root@ALSHBSITL00061 kubernetes]# kubeadm certs renew all [renew] Reading configuration from the cluster... [renew] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml' [renew] Error reading configuration from the Cluster. Falling back to default configuration
certificate embedded in the kubeconfig file for the admin to use and for kubeadm itself renewed certificate for serving the Kubernetes API renewed certificate the apiserver uses to access etcd renewed certificate for the API server to connect to kubelet renewed certificate embedded in the kubeconfig file for the controller manager to use renewed certificate for liveness probes to healthcheck etcd renewed certificate for etcd nodes to communicate with each other renewed certificate for serving etcd renewed certificate for the front proxy client renewed certificate embedded in the kubeconfig file for the scheduler manager to use renewed
Done renewing certificates. You must restart the kube-apiserver, kube-controller-manager, kube-scheduler and etcd, so that they can use the new certificates.
