Kubernetes Solution & Workaround
How to Fix Kubernetes 1.31 Upgrade Issues from 1.30
We see on some Kubernetes cluster upgrading from 1.30 -> 1.31 following errors on cilium, coredns, kube-proxy, ...
The pods will not start on the updated Control Plane, so we must do it with a little workaround to ensure a seamless upgrade.
Upgrade the Cluster without errors:
First of all if you face that problem, no worries, you can easily rollback the kubeadm and patch it then.
How to fix it: Have a look at our Blog to get a step by step manual for it.
