This message was deleted.

https://ranchermanager.docs.rancher.com/troubleshooting/kubernetes-components/troubleshooting-etcd-nodes#defrag-all-etcd-members talks about docker, but rancher is using containerd?

where is that alert or error coming from? that’s not something rke2 would trigger.

Yes I am sure it's an rke2 cluster. The alert is coming from the rancher monitoring package defaults

ah ok yeah. Rancher will provision RKE2 and K3s which both use containerd. It’ll also provision RKE which uses Docker.

I'm k8s tho

But for RKE2, it pretty much self-manages etcd, including defragging it on startup.

Hmm I wonder if it resets the etcd status alarm

the rke2-server service would be on the downstream node. You’ll have to log into it locally to restart it. It’s a systemd unit, not a cluster service.

The local is a K3S I manually installed , the other is a cluster rancher deployed

On the controller host in an emergency situation, I've been able to interact with ``sudo etcdctl --endpoints=127.0.0.1:2379 --cacert=/var/lib/rancher/rke2/server/tls/etcd/server-ca.crt --cert=/var/lib/rancher/rke2/server/tls/etcd/server-client.crt --key=/var/lib/rancher/rke2/server/tls/etcd/server-client.key endpoint status -w table --cluster=true``

Thanks David

Rke2 automatically defrags and clears alarms on startup, so just restart is definitely the easiest way to handle that.