$ kubeadm alpha 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 -oyaml'
CERTIFICATE EXPIRES RESIDUAL TIME CERTIFICATE AUTHORITY EXTERNALLY MANAGED admin.conf Apr 22, 2021 09:03 UTC 364d no apiserver Apr 22, 2021 09:03 UTC 364d ca no apiserver-etcd-client Apr 22, 2021 09:03 UTC 364d etcd-ca no apiserver-kubelet-client Apr 22, 2021 09:03 UTC 364d ca no controller-manager.conf Apr 22, 2021 09:03 UTC 364d no etcd-healthcheck-client Apr 22, 2021 09:03 UTC 364d etcd-ca no etcd-peer Apr 22, 2021 09:03 UTC 364d etcd-ca no etcd-server Apr 22, 2021 09:03 UTC 364d etcd-ca no front-proxy-client Apr 22, 2021 09:03 UTC 364d front-proxy-ca no scheduler.conf Apr 22, 2021 09:03 UTC 364d no
CERTIFICATE AUTHORITY EXPIRES RESIDUAL TIME EXTERNALLY MANAGED ca Apr 14, 2030 11:18 UTC 9y no etcd-ca Apr 14, 2030 11:18 UTC 9y no front-proxy-ca Apr 14, 2030 11:18 UTC 9y no
更新所有证书
1 2 3 4 5 6 7 8 9 10 11 12 13 14
$ kubeadm alpha 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 -oyaml'
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