После развертывания кластера ALT Orchestra рекомендуется проверить состояние системных служб, компонентов Kubernetes и основных сервисов кластера. Для этого можно использовать утилиту talosctl.
9.1. Проверка состояния системных служб
Проверка состояния системных служб на Control Plane-узле:
$ talosctl --talosconfig=./talosconfig -e ${endPoint} -n ${endPoint} service
Ожидаемый вывод:
NODE SERVICE STATE HEALTH LAST CHANGE LAST EVENT
192.168.0.140 apid Running OK 34h16m51s ago Health check successful
192.168.0.140 containerd Running OK 22h27m21s ago Health check successful
192.168.0.140 cri Running OK 6m17s ago Health check successful
192.168.0.140 dashboard Running ? 34h16m57s ago Process Process(["/sbin/dashboard"]) started with PID 2117
192.168.0.140 etcd Running OK 34h15m53s ago Health check successful
192.168.0.140 kubelet Running OK 6m6s ago Health check successful
192.168.0.140 machined Running OK 34h16m59s ago Health check successful
192.168.0.140 syslogd Running OK 34h16m58s ago Health check successful
192.168.0.140 trustd Running OK 34h16m53s ago Health check successful
192.168.0.140 udevd Running OK 34h16m58s ago Health check successful
Проверка состояния системных служб на Worker-узле:
$ talosctl --talosconfig=./talosconfig -e ${endPoint} -n ${workerIP} service
Ожидаемый вывод:
NODE SERVICE STATE HEALTH LAST CHANGE LAST EVENT
192.168.0.145 apid Running OK 34h19m8s ago Health check successful
192.168.0.145 containerd Running OK 34h19m13s ago Health check successful
192.168.0.145 cri Running OK 14m1s ago Health check successful
192.168.0.145 dashboard Running ? 34h19m11s ago Process Process(["/sbin/dashboard"]) started with PID 2122
192.168.0.145 kubelet Running OK 34h17m38s ago Health check successful
192.168.0.145 machined Running OK 34h19m13s ago Health check successful
192.168.0.145 syslogd Running OK 34h19m12s ago Health check successful
192.168.0.145 udevd Running OK 34h19m12s ago Health check successful
Службы должны находиться в состоянии Running, а их состояние здоровья (HEALTH) должно быть OK.
