Closed marrgieD closed 1 year ago
Please use k8s 1.27.2 or later, 1.27.1 had a bug with kubelet not starting static pods correctly.
Please use k8s 1.27.2 or later, 1.27.1 had a bug with kubelet not starting static pods correctly.
But my colleague use 1.27.1 and succeed, his bare metal is on ESXI and mine on VMWare, so I thin 1.27.1 is ok as well. “not starting static pods correctly” is it cannot bootstrap automatically? I usetalosctl bootstrap
to make etcd start. And is 1.27.2 support talos 1.4.0?
Please use k8s 1.27.2 or later, 1.27.1 had a bug with kubelet not starting static pods correctly.
[xxx@localhost talosnew]$ talosctl -n 192.168.242.188 get staticpods
NODE NAMESPACE TYPE ID VERSION
192.168.242.188 k8s StaticPod kube-apiserver 1
192.168.242.188 k8s StaticPod kube-controller-manager 1
192.168.242.188 k8s StaticPod kube-scheduler 1
It seems this is ok
the 1.27.1 bug is intermittent, please upgrade to something above that
please also make sure you have even disk/RAM: https://www.talos.dev/v1.4/introduction/system-requirements/#recommended
Bug Report
Description
I use CentOS7 to installing talos by PXE. It seems like that my enviroment lose some container. Most importantly, there is no container for kube-apiserver, which makes me can do nothing.
I cannot get node
on talos machine always circularly the following two warnings:
And it is not healthy constantly, sometimes unhealthy, and the state always switch to another one for a short time, about several minutes
Logs
Environment
talosctl version v:1.4.0
]