cDR

Maybe this node logs helps ``` 01/01/1970 11:17:24 [talos] node watch error {"component": "controller-runtime", "controller": "k8s.NodeStatusController", "error": "failed to list *v1.Node: Get \"https://127.0.0.1:7445/api/v1/nodes?fieldSelector=metadata.name%3Dtalos-q7f-tv7&resourceVersion=7429241\": EOF", "error_count": 4} 01/01/1970 11:18:08 [talos] node...

The date on the node is correct, it's an optical UI issue in omni, I can reproduce this issue; - stop omni and wait for a few minutes - restart...

Is this an option that can be changed after install? Still facing this issue :(

Hi Smirna, Steps for me to reproduce this issue; - omni 1.45.1, talos 1.9.2 - I run omni in a docker container, I stop the container for 1 minute and...

Some disconnected nodes are actually connected (the metrics and process list updates but the node is marked offline) _The machine is unreachable. The last known state is shown._

Sorry for the screenshots, not the best debug material indeed. One thing that stand out is that a "disconnected" node has metrics but no logs and the node responds to...

I appreciate the support and will continue to investigate this issue. I will give the grpc option a try, that @LM1LC3N7 mentioned

There are 4 critical CVE's in etcd 3.5.10-debian-11-r2 shipped with the chart, can this be updated to the latest version?