kube-controller-manager in CrashLoopBackoff and Error #76069
How to reproduce it (as minimally and precisely as possible):
Below are the error logs from one of the kube-controller-manager pods but I saw this log just ones other logs are given below
Flag --address has been deprecated, see --bind-address instead.
Below is how the pods looks now
kube-controller-manager-stagingmaster1.company.com 0/1 CrashLoopBackOff 106 18h
These are the logs from all the three pods
[root@stagingmaster1 ~]# kubectl logs -n kube-system kube-controller-manager-stagingmaster1.company.com
This has very little resolution available online in all my searches and I could see many people facing it, most of them fixed it by rebuilding the clusters from scratch or doing kubeadm reset when it occurs.
If you need more information please ask
The text was updated successfully, but these errors were encountered:
I also have similar problem. My kube-controller-manager pod in CrashLoopBackoff after the wifi changed.