I am seeing below error running "kubectl get componentstatus".
NAME STATUS MESSAGE ERROR
scheduler Healthy ok
etcd-1 Unhealthy Get https://127.0.0.1:4002/health: remote error: tls: bad certificate
controller-manager Healthy ok
etcd-0 Unhealthy Get https://127.0.0.1:4001/health: remote error: tls: bad certificate
And observed one of the three master nodes in NotReady state. The state of the other 2 master nodes and all other worker nodes seems to be fine
I have connected to the master which is having the issue and tried to check if certificates under /etc/kubernetes/pki but none of the certificates are showing as expired.
Faced similar issue earlier and resolved it following the article (https://kops.sigs.k8s.io/advisories/etcd-manager-certificate-expiration/)
Following are kops and kubectl version details
kubectl verison
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.7", GitCommit:"6c143d35bb11d74970e7bc0b6c45b6bfdffc0bd4", GitTreeState:"clean", BuildDate:"2019-12-11T12:34:17Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
kops version
Version 1.15.3 (git-298c2fce8)
Pls help