Noel Georgi

> I was upgrading a single control-plane node with talosctl -n upgrade --image ghcr.io/siderolabs/installer:v1.1.0. apologies, I mistakenly assumed from the above message you had a single control plane node. What...

>maybe that is a problem with the Talos Discovery Service and a long ttl the default ttl is 30mins, it's recommended to create a new set of machine config for...

I believe a second option is more suitable and build a custom image using `imager`. I thought of having a single run extension service which would read a file on...

> on rpi4 looks like etcd might be an amd64 binary instead of arm64, I am running talos v1.1.2 on rpi4b it's the job of CRI to pull the right...

seems the install is completely broken, could you re-flash and try again

what does `talosctl containers -k` show and also `talosctl logs -k `, it seems there's is some issue with the generated config probably. It would be nice if you could...

did you set the kernel arg or the sysctl? As per release notes, it can't be sysctl. ```text When kexec support is disabled (see `Reboots via kexec`), Talos no longer...

also the `kernelArgs` only take effect on a talos upgrade

the idea is here to use something along the lines of `talosctl -l control-plane get links` , wehre `control-plane` a node label assigned outside kubernetes

can you check the logs from `/var/log/containers`, there should be one for apiserver if it ever started