Работоспособность
Проверка списка и работоспособности компонентов kubernetes в кластере на узлах ALT Orchestra
Controlplane узел:
console
$ talosctl --talosconfig=./talosconfig -e ${endPoint} -n ${endPoint} service
NODE SERVICE STATE HEALTH LAST CHANGE LAST EVENT
192.168.122.172 apid Running OK 34h16m51s ago Health check successful
192.168.122.172 containerd Running OK 22h27m21s ago Health check successful
192.168.122.172 cri Running OK 6m17s ago Health check successful
192.168.122.172 dashboard Running ? 34h16m57s ago Process Process(["/sbin/dashboard"]) started with PID 2117
192.168.122.172 etcd Running OK 34h15m53s ago Health check successful
192.168.122.172 kubelet Running OK 6m6s ago Health check successful
192.168.122.172 machined Running OK 34h16m59s ago Health check successful
192.168.122.172 syslogd Running OK 34h16m58s ago Health check successful
192.168.122.172 trustd Running OK 34h16m53s ago Health check successful
192.168.122.172 udevd Running OK 34h16m58s ago Health check successfulWorker узел:
console
$ talosctl --talosconfig=./talosconfig -e ${endPoint} -n ${workerIP} service
NODE SERVICE STATE HEALTH LAST CHANGE LAST EVENT
192.168.122.43 apid Running OK 34h19m8s ago Health check successful
192.168.122.43 containerd Running OK 34h19m13s ago Health check successful
192.168.122.43 cri Running OK 14m1s ago Health check successful
192.168.122.43 dashboard Running ? 34h19m11s ago Process Process(["/sbin/dashboard"]) started with PID 2122
192.168.122.43 kubelet Running OK 34h17m38s ago Health check successful
192.168.122.43 machined Running OK 34h19m13s ago Health check successful
192.168.122.43 syslogd Running OK 34h19m12s ago Health check successful
192.168.122.43 udevd Running OK 34h19m12s ago Health check successfulПроверка доступности сервисов (healthcheck)
console
$ talosctl --talosconfig=./talosconfig -e ${endPoint} -n ${endPoint} health
discovered nodes: ["192.168.122.43" "192.168.122.172"]
waiting for etcd to be healthy: ...
waiting for etcd to be healthy: OK
waiting for etcd members to be consistent across nodes: ...
waiting for etcd members to be consistent across nodes: OK
waiting for etcd members to be control plane nodes: ...
waiting for etcd members to be control plane nodes: OK
waiting for apid to be ready: ...
waiting for apid to be ready: OK
waiting for all nodes memory sizes: ...
waiting for all nodes memory sizes: OK
waiting for all nodes disk sizes: ...
waiting for all nodes disk sizes: OK
waiting for no diagnostics: ...
waiting for no diagnostics: OK
waiting for kubelet to be healthy: ...
waiting for kubelet to be healthy: OK
waiting for all nodes to finish boot sequence: ...
waiting for all nodes to finish boot sequence: OK
waiting for all k8s nodes to report: ...
waiting for all k8s nodes to report: OK
waiting for all control plane static pods to be running: ...
waiting for all control plane static pods to be running: OK
waiting for all control plane components to be ready: ...
waiting for all control plane components to be ready: OK
waiting for all k8s nodes to report ready: ...
waiting for all k8s nodes to report ready: OK
waiting for kube-proxy to report ready: ...
waiting for kube-proxy to report ready: OK
waiting for coredns to report ready: ...
waiting for coredns to report ready: OK
waiting for all k8s nodes to report schedulable: ...
waiting for all k8s nodes to report schedulable: OKСтатистика
Сервисов talos:
console
$ talosctl --talosconfig=./talosconfig -e ${endPoint} -n ${endPoint} stats
NODE NAMESPACE ID MEMORY(MB) CPU
192.168.122.172 system apid 17.66 12755669000
192.168.122.172 system trustd 10.76 11336251000Сервисов kubernetes:
console
$ talosctl --talosconfig=./talosconfig -e ${endPoint} -n ${endPoint} stats -k
NODE NAMESPACE ID MEMORY(MB) CPU
192.168.122.172 k8s.io kube-system/coredns-5c584f8977-nctvv 0.00 0
192.168.122.172 k8s.io └─ kube-system/coredns-5c584f8977-nctvv:coredns:7b0dd9383da7 23.88 7867830000
192.168.122.172 k8s.io kube-system/coredns-5c584f8977-t55cr 0.00 0
192.168.122.172 k8s.io └─ kube-system/coredns-5c584f8977-t55cr:coredns:c34642e2a12c 23.55 7406138000
192.168.122.172 k8s.io kube-system/kube-apiserver-talos-vt1-w8a 0.00 0
192.168.122.172 k8s.io └─ kube-system/kube-apiserver-talos-vt1-w8a:kube-apiserver:59f85fddee5a 356.34 12322845633000
192.168.122.172 k8s.io kube-system/kube-controller-manager-talos-vt1-w8a 0.00 0
192.168.122.172 k8s.io └─ kube-system/kube-controller-manager-talos-vt1-w8a:kube-controller-manager:682d16de34fb 0.00 0
192.168.122.172 k8s.io └─ kube-system/kube-controller-manager-talos-vt1-w8a:kube-controller-manager:c42ebf483f1a 93.95 40557624000
192.168.122.172 k8s.io kube-system/kube-flannel-vzvzx 0.00 0
192.168.122.172 k8s.io └─ kube-system/kube-flannel-vzvzx:install-config:494eaa3616eb 0.00 0
192.168.122.172 k8s.io └─ kube-system/kube-flannel-vzvzx:kube-flannel:518979a3ecfb 19.67 859609411000
192.168.122.172 k8s.io kube-system/kube-proxy-9rmz2 0.00 0
192.168.122.172 k8s.io └─ kube-system/kube-proxy-9rmz2:kube-proxy:fc588cf68e08 25.46 38185553000
192.168.122.172 k8s.io kube-system/kube-scheduler-talos-vt1-w8a 0.00 0
192.168.122.172 k8s.io └─ kube-system/kube-scheduler-talos-vt1-w8a:kube-scheduler:21e57ea3d010 30.48 8256563000
192.168.122.172 k8s.io └─ kube-system/kube-scheduler-talos-vt1-w8a:kube-scheduler:2f741e23c919 0.00 0Комплексный тест kubernetes-кластера
Требует, чтобы как минимум два узла в кластере могли запускать не системные POD'ы. Если узел worker всего один, необходимо сделать untaint на controlplane-узлы.
console
$ talosctl --talosconfig=./talosconfig -e ${endPoint} -n ${endPoint} conformance kubernetes
running conformance tests version 1.31.1
running tests: \[Conformance\]
2025/01/29 13:34:23 Running command:
Command env: []
Run from directory:
Executable path: /usr/local/bin/ginkgo
Args (comma-delimited): /usr/local/bin/ginkgo,--focus=\[Conformance\],--skip=,--no-color=true,--procs=4,--timeout=24h,/usr/local/bin/e2e.test,--,--disable-log-dump,--repo-root=/kubernetes,--provider=skeleton,--report-dir=/tmp/results,--kubeconfig=
2025/01/29 13:34:23 Now listening for interrupts
Running Suite: Kubernetes e2e suite - /usr/local/bin
====================================================
Random Seed: 1738157663 - will randomize all specs
Will run 404 of 6603 specs
....
Summarizing 2 Failures:
[FAIL] [sig-scheduling] SchedulerPredicates [Serial] [It] validates resource limits of pods that are allowed to run [Conformance] [sig-scheduling, Serial, Conformance]
k8s.io/kubernetes/test/e2e/scheduling/predicates.go:414
[FAIL] [sig-apps] Daemon set [Serial] [It] should rollback without unnecessary restarts [Conformance] [sig-apps, Serial, Conformance]
k8s.io/kubernetes/test/e2e/apps/daemon_set.go:446
Ran 404 of 6603 Specs in 2842.641 seconds
FAIL! -- 402 Passed | 2 Failed | 0 Pending | 6199 Skipped
Ginkgo ran 1 suite in 47m26.014915675s
tests finished after 47m26s.