You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Same report here #2699 but we suspected it was ha proxy. Make sure nothing is stripping headers in your network setup. We don't have such problems in our CI.
The crash looping can be caused by container runtime problems or network peoblems and you need to look at the kubelet and container logs.
Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT
Versions
kubeadm version (use
kubeadm version
):kubeadm version: &version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.1", GitCommit:"3ddd0f45aa91e2f30c70734b175631bec5b5825a", GitTreeState:"clean", BuildDate:"2022-05-24T12:24:38Z", GoVersion:"go1.18.2", Compiler:"gc", Platform:"linux/amd64"}
Environment:
kubectl version
):Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.1", GitCommit:"3ddd0f45aa91e2f30c70734b175631bec5b5825a", GitTreeState:"clean", BuildDate:"2022-05-24T12:26:19Z", GoVersion:"go1.18.2", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
x86_64, AMD Ryzen 5 3600 6-Core Processor, 64GB RAM, 2TB HDD
Ubuntu 22.04 LTS
uname -a
):5.15.0-33-generic #34-Ubuntu SMP Wed May 18 13:34:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
containerd
Calico
Currently resetted kubeadm again and not yet added Calico.
What happened?
Ran
Init failed in phase [addons].
Tried to ran phase manually with
Was successful.
But kube-controller-manager, kube-proxy and kube-scheduler constantly have CrashLoopBackOff
Tried to restart kubelet. But right after restart again in CrashLoopBackOff. After some time kubelet isn't reachable and i get the following message:
What you expected to happen?
Successful init and a running controller node with coredns, etcd, kube-apiserver, kubecontroller-manager, kube-proxy, kube-scheduler
How to reproduce it (as minimally and precisely as possible)?
Running
With a kubeadm-config.yaml that looks like:
Anything else we need to know?
According to this page, there should be no CrashLoopBackOffs right after kubeadm init
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/
Tried to start from this tutorial:
https://jimangel.io/post/dockershim-kubernetes-v1.24/
Came until "Deploy a “hello-world” workload"
After that had various kublet restarts and kubeadm reset and inits
The text was updated successfully, but these errors were encountered: