[bug] Authorization error on apiserver-kubelet-client

[dfense23]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I have a cluster in my home. After a hardware failure on the network and setting up the new network, all IPs changed.

Now my cluster is down, with no available Controlplanes (All in status booting)
The errors on the dashboard are mainly:
error fetching pod status: "Authorization error (user=api-server-kubelet-client, verb=get, resource=node, subresource=pods) has prevented the request from succeeding.

A websearch pointed me in the direction that the new IPs are missing in the certificates, but I was not able to find a solution. Any help would be appreciated.

[talos] task startAllServices (1/1): service "etcd" to be "up"

[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%3Domni-hocp04&limit=500&resourceVersion=0\": EOF", "error_count": 3}

[talos] controller failed {"component": "controller-runtime", "controller": "k8s.KubeletStaticPodController", "error": "error refreshing pod status: error fetching pod status: an error on the server ("Authorization error (user=apiserver-kubelet-client, verb=get, resource=nodes, subresource=pods)") has prevented the request from succeeding"}
19/11/2025 23:06:49
[talos] task startAllServices (1/1): service "etcd" to be "up"

[talos] kubernetes endpoint watch error {"component": "controller-runtime", "controller": "k8s.EndpointController", "error": "failed to list *v1.EndpointSlice: Get "https://[fdae:41e4:649b:9303::1]:10000/apis/discovery.k8s.io/v1/namespaces/default/endpointslices?fieldSelector=metadata.name%3Dkubernetes&limit=500&resourceVersion=0": EOF"}

[talos] controller failed {"component": "controller-runtime", "controller": "k8s.NodeApplyController", "error": "1 error(s) occurred:\n\ttimeout"}

Expected Behavior

Cluster up, restored.

Steps To Reproduce

I cannot really reproduce it and understand this might not really be a bug. But according to the link in the Omni Doc this is the place to ask. If this is wrong, sorry, then just close and it would be appreciated if you could point me in the right direction.

What browsers are you seeing the problem on?

Firefox

Anything else?

No response

[Unix4ever]

I think nothing works as etcd is not healthy.
You might need to check the etcd logs.

Also if you use DHCP, I'd recommend pinning the IPs on the router, as Kubernetes doesn't like IPs being changed.