Scotte Zinn

specifically the one for logging: machine: install: extraKernelArgs: - talos.logging.kernel=tcp://host:5044/ I think the expectation would be that at the end of the editmachineconfig and a talosctl upgrade that the grub...

Thanks for the info. My original controlplane.yaml has ``` cluster: network: cni: name: custom urls: - http://router/staging-cilium-quick-install.yaml ``` to define the cilium CNI. If I understand what you are saying,...

Also looks like the upgrade is expecting a siderolabs 1.23.7 kubelet which doesn't appear to be available yet.

Let me know if it is indeed caching the original manifests from the initial node configuration - it kind of looks like it did. I continued with the upgrade and...

Rebooted with 1.0.1 and the node came up - however, /system/secrets/kubernetes/kube-controller-manager/kubeconfig still referred to localhost

$ talosctl c -k -n 10.0.40.64 NODE NAMESPACE ID IMAGE PID STATUS [kubelet.log](https://github.com/siderolabs/talos/files/8612610/kubelet.log) /var/log/pods is empty

$ talosctl -n 10.0.40.64 ls /etc/kubernetes/manifests/ NODE NAME 10.0.40.64 . 10.0.40.64 talos-kube-apiserver.yaml 10.0.40.64 talos-kube-controller-manager.yaml 10.0.40.64 talos-kube-scheduler.yaml

Rolling kubelet back to 1.23.5 unblocked it and node came up. It was 1.23.6 previously

Also, if I do talosctl reset -n 10.0.40.64, the process gets bogged down because the registry node watch fails since the VIP address has already been taken down. The machine...

Agreed on the red herring and also that kubelet is perhaps getting started before the static pod definition is fully written? Restarting it picks up the updated info and all...