This message was deleted.
# k3s
a
This message was deleted.
c
If the service is running, it's connected. If it cant connect to any server, the service will exit and be restarted continuously by systemd until it can get a connection.
So, just a basic service uptime/restart counter check should suffice for gross health checking
If you need something more granular than that, the kubelet has a poorly documented API that you could probably query
c
Awesome, it sounds like just checking the systemd service status will actually work for me then!