Kubernetes Errors: weave-net pod CrashLoopBackOff

Errors

[ec2-user@ip-172-31-16-114 ~]$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                                                   READY   STATUS             RESTARTS   AGE
kube-system   etcd-ip-172-31-16-114.ap-south-1.compute.internal                      1/1     Running            1          20h
kube-system   kube-apiserver-ip-172-31-16-114.ap-south-1.compute.internal            1/1     Running            1          20h
kube-system   kube-controller-manager-ip-172-31-16-114.ap-south-1.compute.internal   1/1     Running            1          17h
kube-system   kube-proxy-nrkj6                                                       1/1     Running            0          15m
kube-system   kube-proxy-zt88q                                                       1/1     Running            1          20h
kube-system   kube-scheduler-ip-172-31-16-114.ap-south-1.compute.internal            1/1     Running            1          20h
kube-system   weave-net-g778b                                                        1/2     CrashLoopBackOff   6          11m
kube-system   weave-net-pts7p                                                        1/2     CrashLoopBackOff   6Code language: JavaScript (javascript)

Solutions

• https://stackoverflow.com/questions/39872332/how-to-fix-weave-net-crashloopbackoff-for-the-second-node

Rajesh Kumar

I’m a DevOps/SRE/DevSecOps/Cloud Expert passionate about sharing knowledge and experiences. I have worked at Cotocus. I share tech blog at DevOps School, travel stories at Holiday Landmark, stock market tips at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow , and SEO strategies at Wizbrand.

Do you want to learn Quantum Computing?

Please find my social handles as below;

Rajesh Kumar Personal Website
Rajesh Kumar at YOUTUBE
Rajesh Kumar at INSTAGRAM
Rajesh Kumar at X
Rajesh Kumar at FACEBOOK
Rajesh Kumar at LINKEDIN
Rajesh Kumar at WIZBRAND

Rajesh Kumar DailyLogs