This message was deleted.
# k3sa
adamant-kite-43734
08/30/2023, 10:16 AMThis message was deleted.
c
creamy-pencil-82913
08/30/2023, 3:33 PMWait so you changed the master IP, and then reconfigured the agents? Or you did not, and some of them are stuck disconnected?
creamy-pencil-82913
08/30/2023, 3:35 PMTo answer your question though - I would just look into monitoring the Kubernetes components themselves. Have you looked into the kubelet’s healthz endpoint?
creamy-pencil-82913
08/30/2023, 3:38 PMThis would be
<http://127.0.0.1:10248/healthz>a
alert-policeman-61846
08/30/2023, 4:30 PMthks @creamy-pencil-82913 Yes we replaced a master with a new master on a different ip. Then restarted the agents (same registration ip, we use a vip).
Il try to check kubelet healthz
alert-policeman-61846
08/30/2023, 4:37 PM Copy code
agents/b13a1d4d-4db4-49d7-a770-d2bf36122402:~# curl <http://127.0.0.1:10248/healthz> -vvv
* Trying 127.0.0.1:10248...
* Connected to 127.0.0.1 (127.0.0.1) port 10248 (#0)
> GET /healthz HTTP/1.1
> Host: 127.0.0.1:10248
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: text/plain; charset=utf-8
< X-Content-Type-Options: nosniff
< Date: Wed, 30 Aug 2023 16:35:52 GMT
< Content-Length: 2
<
* Connection #0 to host 127.0.0.1 left intactđź‘Ť 1
6 Views