Why talos state become not ready?

[O-corn]

I created a pod with one container included, and ran a workload in it. After a while, the state of talos turn to READY:false, and it removed my ip. Few minutes later, the state of kubelet, Apiserver, controller-manage, scheduler become n/a. Could you give me some hints to debug on this problem?

[O-corn]

When state of kubelet, Apiserver, controller-manage, scheduler become n/a, I noticed that the workload is still running, because from the console I can see the cpu usage is still high.

[smira]

Please submit the text version of the logs, preferably output of talosctl support.

[O-corn]

After the system crashed, I cannot communicate with the system by talosctl(since the ip is removed, don't know the reason), so talosctl dmesg got stuck..... I can only see the logs on the screen...... or do you have some hints on getting the text version of system logs?

[smira]

You have two IPs listed on your screenshot, where do they come from?

[smira]

There's no way we could help without you providing some information, you can reboot your machine and run talosctl support.