134
edits
Mich181189 (talk | contribs) |
Mich181189 (talk | contribs) |
||
| Line 183: | Line 183: | ||
# Run <code>kubeadm reset</code> on the affected node | # Run <code>kubeadm reset</code> on the affected node | ||
# Run <code>kubeadm join</code> as if it was a new node | # Run <code>kubeadm join</code> as if it was a new node | ||
== ETCD Maintainance == | |||
It seems the ETCD database can grow very, very large, which can cause startup to take many minutes, making many things unhappy. | |||
Running this on the master can help: | |||
ETCDCTL_API=3 etcdctl --cacert=/etc/kubernetes/pki/etcd/ca.crt --cert=/etc/kubernetes/pki/etcd/server.crt --key=/etc/kubernetes/pki/etcd/server.key get revisiontestkey -w json | |||
{"header":{"cluster_id":12152285089840826538,"member_id":17687274478532125122,"revision":45368346,"raft_term":10}} | |||
take the revision from above, subtract one, then run: | |||
ETCDCTL_API=3 etcdctl --cacert=/etc/kubernetes/pki/etcd/ca.crt --cert=/etc/kubernetes/pki/etcd/server.crt --key=/etc/kubernetes/pki/etcd/server.key compact 45368345 | |||
ETCDCTL_API=3 etcdctl --cacert=/etc/kubernetes/pki/etcd/ca.crt --cert=/etc/kubernetes/pki/etcd/server.crt --key=/etc/kubernetes/pki/etcd/server.key defrag | |||