omni/internal/backend/dns
Artem Chernyshev 28158ed855
Some checks are pending
default / default (push) Waiting to run
default / e2e-backups (push) Blocked by required conditions
default / e2e-cluster-import (push) Blocked by required conditions
default / e2e-forced-removal (push) Blocked by required conditions
default / e2e-omni-upgrade (push) Blocked by required conditions
default / e2e-scaling (push) Blocked by required conditions
default / e2e-short (push) Blocked by required conditions
default / e2e-short-secureboot (push) Blocked by required conditions
default / e2e-templates (push) Blocked by required conditions
default / e2e-upgrades (push) Blocked by required conditions
default / e2e-workload-proxy (push) Blocked by required conditions
fix: ignore MachineStatus having no TalosVersion in DNS service
We can probably tolerate it being empty in the Talos request proxying.
Otherwise the behavior is confusing: the node is connected, but it's not
possible to reach it with `talosctl` using the node UUID.

Signed-off-by: Artem Chernyshev <artem.chernyshev@talos-systems.com>
2025-07-23 19:46:01 +03:00
..
service_test.go chore: rekres, bump deps, Go, Talos and k8s versions, satisfy linters 2025-07-11 18:23:48 +02:00
service.go fix: ignore MachineStatus having no TalosVersion in DNS service 2025-07-23 19:46:01 +03:00