Source: itnext.io
Breaking down and fixing etcd clusterCategory: Database, Data, Kubernetes
It is at the heart of Kubernetes and is an integral part of its control-plane.
In the previous article, we looked in detail at regenerating SSL-certificates and static-manifests for Kubernetes, as well as issues related to restoring the operability of its control-plane.
However, this is already beyond the scope of this article.If something has gonna wrong and you can’t exec into a running container, look at the etcd logs:crictl logs "$CONTAINER_ID"And also make sure you have a static manifest and all certificates in case the container is not even existing.
The second option is more accurate, since it allows you to consider and make changes that are necessary only for etcd.
But in this case, we need to specify all the nodes of our cluster in the options to etcdctl command, for example: for node1: for node2: for node3: Sometimes it happens that you have lost most of the nodes from the cluster and etcd went into an inoperative state.
In the previous article, we looked in detail at regenerating SSL-certificates and static-manifests for Kubernetes, as well as issues related to restoring the operability of its control-plane.
However, this is already beyond the scope of this article.If something has gonna wrong and you can’t exec into a running container, look at the etcd logs:crictl logs "$CONTAINER_ID"And also make sure you have a static manifest and all certificates in case the container is not even existing.
The second option is more accurate, since it allows you to consider and make changes that are necessary only for etcd.
But in this case, we need to specify all the nodes of our cluster in the options to etcdctl command, for example: for node1: for node2: for node3: Sometimes it happens that you have lost most of the nodes from the cluster and etcd went into an inoperative state.
Related Articles
Community Partners
DevOps Careers