kubeadm启动失败
来源:1-1 课程介绍

慕村5588232
2022-12-19
老师你好,我想要基于vmware的centos7虚拟机用kubeadm+haproxy+keepalived搭建一个k8s 1.25.0的集群。大概是下面这个结构
/etc/hosts
192.168.0.151 k8s-ha01.example.local k8s-ha01
192.168.0.152 k8s-ha02.example.local k8s-ha02
192.168.0.161 k8s-master01.example.local k8s-master01
192.168.0.162 k8s-master02.example.local k8s-master02
192.168.0.163 k8s-master03.example.local k8s-master03
192.168.0.171 k8s-harbor01.example.local k8s-harbor01
192.168.0.172 k8s-harbor02.example.local k8s-harbor02
192.168.0.181 k8s-node01.example.local k8s-node01
192.168.0.182 k8s-node02.example.local k8s-node02
192.168.0.183 k8s-node03.example.local k8s-node03
192.168.0.188 kubeapi.eugene.cc kubeapi
然后kubeadm init每次都会超时报错
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory “/etc/kubernetes/manifests”. This can take up to 4m0s
I1219 18:42:51.443726 80554 with_retry.go:242] Got a Retry-After 1s response for attempt 7 to https://kubeapi.eugene.cc:8443/healthz?timeout=10s
完整的init命令:
kubeadm init --control-plane-endpoint “kubeapi.eugene.cc:8443” --upload-certs --kubernetes-version=1.25.0 --image-repository registry.aliyuncs.com/google_containers --service-cidr=10.96.0.0/16 --cri-socket unix:///run/containerd/containerd.sock --pod-network-cidr=10.244.0.0/16 --skip-phases=addon/kube-proxy
1回答
-
刘果国
2022-12-20
kubeadm一般都是网络相关问题,可以多试几次,或找一下日志,看看卡的点00
相似问题