k8s [kubelet-check] Initial timeout of 40s passed.解决方案

最新推荐文章于 2024-05-10 21:30:38 发布
最新推荐文章于 2024-05-10 21:30:38 发布
阅读量4.1w 收藏 32
点赞数 14
分类专栏： Linux技术 文章标签： kubernetes centos docker
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_44789466/article/details/119046245
版权

[kubelet-check] Initial timeout of 40s passed.解决方案

解决方案

环境：
CentOS 7.9
Kubernetes 1.19.0
docker-ce 19.03.5

解决方案

第1步：
将init-config.yaml 中的 advertiseAddress: 1.2.3.4 修改为advertiseAddress: 10.0.128.0，其中10.0.128.0为 master节点的ip地址。
第2步：

$ kubeadm reset

第3步

$ kubeadm init --config=init-config.yaml

我的 init-config.yaml 文件（供参考）

apiVersion: kubeadm.k8s.io/v1beta2
bootstrapTokens:
- groups:
  - system:bootstrappers:kubeadm:default-node-token
  token: abcdef.0123456789abcdef
  ttl: 24h0m0s
  usages:
  - signing
  - authentication
kind: InitConfiguration
localAPIEndpoint:
  advertiseAddress: 10.0.128.0
  bindPort: 6443
nodeRegistration:
  criSocket: /var/run/dockershim.sock
  name: k8s-master
  taints:
  - effect: NoSchedule
    key: node-role.kubernetes.io/master
---
apiServer:
  timeoutForControlPlane: 4m0s
apiVersion: kubeadm.k8s.io/v1beta2
certificatesDir: /etc/kubernetes/pki
clusterName: kubernetes
controllerManager: {}
dns:
  type: CoreDNS
etcd:
  local:
    dataDir: /var/lib/etcd
imageRepository: registry.aliyuncs.com/google_containers
kind: ClusterConfiguration
kubernetesVersion: v1.19.0
networking:
  dnsDomain: cluster.local
  podsubnet: 192.168.0.0/16
  serviceSubnet: 10.96.0.0/16
scheduler: {}

遇到该问题的历程

[root@k8s-master ~]# kubeadm init --config=init-config.yaml
W0723 23:07:55.124557   56762 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[init] Using Kubernetes version: v1.19.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [k8s-master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 1.2.3.4]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [k8s-master localhost] and IPs [1.2.3.4 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [k8s-master localhost] and IPs [1.2.3.4 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[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
[kubelet-check] Initial timeout of 40s passed.

	Unfortunately, an error has occurred:
		timed out waiting for the condition

	This error is likely caused by:
		- The kubelet is not running
		- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

	If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
		- 'systemctl status kubelet'
		- 'journalctl -xeu kubelet'

	Additionally, a control plane component may have crashed or exited when started by the container runtime.
	To troubleshoot, list all containers using your preferred container runtimes CLI.

	Here is one example how you may list all Kubernetes containers running in docker:
		- 'docker ps -a | grep kube | grep -v pause'
		Once you have found the failing container, you can inspect its logs with:
		- 'docker logs CONTAINERID'

error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher

翻遍了百度谷歌github，然并卵。。
直到遇到了这篇文章
https://q.cnblogs.com/q/124859/
按照大佬的方法，将 yaml 文件中的 advertiseAddress 修改为 k8s.cnlogs.com ，并在 hosts 中将 k8s.cnblogs.com 解析到 master 节点的本机 IP 地址，修改完成后报错如下。

[root@k8s-master ~]# kubeadm init --config=init-config.yaml
couldn't use "k8s.cnlogs.com" as "apiserver-advertise-address", must be ipv4 or ipv6 address
To see the stack trace of this error execute with --v=5 or higher

灵机一动，直接将 advertiseAddress 修改为 master 节点 ip 地址，问题解决。

[root@k8s-master ~]# kubeadm init --config=init-config.yaml
W0723 23:48:02.401877   74798 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[init] Using Kubernetes version: v1.19.0
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [k8s-master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.128.0]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [k8s-master localhost] and IPs [10.0.128.0 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [k8s-master localhost] and IPs [10.0.128.0 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[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
[apiclient] All control plane components are healthy after 6.002090 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.19" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node k8s-master as control-plane by adding the label "node-role.kubernetes.io/master=''"
[mark-control-plane] Marking the node k8s-master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: abcdef.0123456789abcdef
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to get nodes
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 10.0.128.0:6443 --token abcdef.0123456789abcdef \
    --discovery-token-ca-cert-hash sha256:6bdcf88c58234831bf230cb3836e892d6ae5c007be6093dcc7c699058220d9d8

参考文章

https://q.cnblogs.com/q/124859/

甲基橙MO
关注
  • 14
    点赞
  • 踩
  • 32
    收藏
    觉得还不错? 一键收藏
  • 9
    评论
专栏目录
kubeadm init初始化k8s集群时报错，[kubelet-check] Initial timeout of 40s passed.
WinterPirates的博客
07-25 5万+
在使用kubeadm init初始化k8s集群中的master主节点时，总是出错。这个地方卡了我很长时间，遇到了好几个不一样的错误，有的问题在网上也没有找到什么有效的解决方案，所以特此记录一下。以下错误均是在使用kubeadm init语句初始化k8s集群过程中出现的问题。 第一次初始化集群时，我的初始化master节点kubeadm init语句为： kubeadm init --kubernetes-version=v1.10.0 \ --apiserver-advertise-address=50.
k8s宕机pod自动迁移方案
07-24
k8s宕机pod自动迁移方案
kubeadm init 初始化运行到 Initial timeout of 40s passed 后报错
chenkewen2007的博客
02-08 3065
kubeadm init 初始化报错
k8s搭建安装init，初始化时报错，解决方案[kubelet-check] Initial timeout of 40s passed.
最新发布
qq_29531077的博客
05-10 1598
根据上述描述，是因为“kebernetes默认设置cgroup驱动为systemd，而docker服务的cgroup驱动为cgroupfs”，有两种决解决方式，方式一，将docker的服务配置文件修改为何kubernetes的相同，方式二是修改kebernetes的配置文件为cgroupfs，这里采用第一种。修改docker服务的配置文件，“/etc/docker/daemon.json ”文件，添加如下。
k8s节点加入master节点时超时：Initial timeout of 40s passed
热门推荐
u012034742的专栏
11-14 1万+
今天误操作，执行yum update时将kubeadm kubectl 跨版本升级了；由1.17.4升级到1.22.3，从而导致集群部分节点不可用。还好是自己电脑上搭建的测试集群。 解决该问题花了很长时间，现在对遇到的问题进行总结。 在master节点下执行，kubectl version 可以看到客户端和服务端的版本不一致。 Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c9
k8s执行init时出现 Initial timeout of 40s passed
weixin_50708603的博客
05-31 4464
环境centOS 7 腾讯云轻量服务器 docker版本 docker-ce-18.06.1.ce-3.el7 kubelet版本 kubelet-1.18.0 kubeadm-1.18.0 kubectl-1.18.0 出现40s的第一个坑 hostnamectl --static set-hostname master 这个主机名不要出现大写..最好也不要出现特殊符号 跟着教程来 在修改/etc/hosts 文件时的主机名也不要出现大写 出现40s的第二个坑 如果...
k8s初始化报错[kubelet-check] Initial timeout of 40s passed.
weixin_46601322的博客
09-06 1万+
k8s初始化报错[kubelet-check] Initial timeout of 40s passed.
kubernetes--技术文档--安装kubernetes集群报错[kubelet-check] Initial timeout of 40s passed.(已经解决)
阿丹的博客
08-21 1163
advertiseAddress: ip # apiserver地址，因为单master，所以配置master的节点内网IP。使用命令查看docker中的容器启动情况。查看日志发现ip没有能绑定。发现组件etcd组件出现问题。重置k8s,进行重新初始化。
K8S初始化master遇到timeout问题：[kubelet-check] Initial timeout of 40s passed.
I_No_dream的博客
07-03 5904
在搭建K8S集群时，遇到master初始化超时问题 如图： 初始化命令：–v=6 打印详细日志 kubeadm init --config kubeadm.yaml --ignore-preflight-errors=all --v=6 因为 解决方案：在/etc/hosts 添加 127.0.0.1 localhost重新执行初始化命令后 初始化成功：succossfully！ 逐个执行所提示命令： mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/ad
kubeadm init执行提示 [kubelet-check] Initial timeout of 40s passed.
czhhhhhhh的博客
11-10 1947
3.网上查了很多资料，并没有有效的解决方式，查看kubelet日志或docker日志都没有有效的信息，后面发现 步骤2执行过程中提示 "/etc/kubernetes/admin.conf"和"/etc/kubernetes/kubelet.conf" 相关文件已存在，然后将其这两个删除，重新执行kubeadm init就成功生成 join信息串了。1.搭建过程执行kubeadm init时，提示超时。
血泪史： k8s Initial timeout of 40s passed.
Vv的博客
03-12 3067
背景： k8s不管是 kubeadm init 和join都会报错 kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml" [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env" [kubelet-start] Starting the ku
k8s安装会遇到的小问题
zeorg的博客
01-09 732
如果遇到[kubelet-check] Initial timeout of 40s passed. 问题，查看日志有可能是k8s 新版本不支持docker的原因 （此现象是docker启动了k8s容器但是会自动杀死容器） 解决办法 查看k8s版本（安装指定版本k8s） 查看docker版本（安装指定版本docker） 还有一种就是由于大意IP地址设置错误 kubeadm init --kubernetes-version=v1.19.4 --pod-network-cidr=10.244.0.0/16 -
阿里云ECS服务器安装kubernetes1.16.0 kubeadm init所遇到的Initial timeout of 40s passed问题
weixin_40668374的博客
10-20 3470
阿里云ECS服务器安装kubernetes1.16.0 kubeadm init所遇到的Initial timeout of 40s passed问题 问题： 创建init文件 kubeadm config print init-defaults > /k8s/kubeadm.yaml 修改文件 vim /k8s/kubeadm.yaml apiVersion: kubeadm.k8s.io/v1beta2 bootstrapTokens: - groups: - system:bootstr
k8s搭集群初始化的坑 k8s Initial timeout of 40s passed
weixin_42541360的博客
12-30 3786
搭建集群参考的博客： https://www.skynemo.cn/2021/02/18/%E5%AE%B9%E5%99%A8%E5%8F%8A%E8%99%9A%E6%8B%9F%E5%8C%96/k8s_install_with_kubeadm/ 第一次初始化的时候没问题，后面重新初始化就报错， 找到一个解决办法， https://blog.csdn.net/weixin_40161254/article/details/112232302 感谢 ...
[kubelet-check] The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘ failed with error:
ck784101777的博客
11-20 1万+
可能性1:10-kubeadm.conf文件缺失 vim /etc/systemd/system/kubelet.service.d/10-kubeadm.conf # Note: This dropin only works with kubeadm and kubelet v1.11+ [Service] Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.con
从节点加入集群时报错Initial timeout of 40s passed.It seems like the kubelet isn‘t running...
star的博客
09-04 1234
将从节点加入集群时报错： 根据框中的问题“error execution phase kubelet-start: error uploading crisocket: timed out waiting for the condition”，解决办法如下： swapoff -a kubeadm reset systemctl daemon-reload systemctl restart kubelet iptables -F && iptables -t nat -F &&a
centos7初始化k8s超时
weixin_45714040的博客
08-16 2173
K8s初始化超时 k8s初始化超时，如下 百度了一下超时的原因，看来看去就一个“血泪史：k8s Initial timeout of 40s passed.”按照博主的方法去修改如下配置文件 注：kubelet版本按照自己的版本来就行 cd /etc/systemd/system/kubelet.service.d sudo vim 10-kubeadm.conf # Note: This dropin only works with kubeadm and kubelet v1.11+ [Servi
k8s初始化报错[kubelet-check] It seems like the kubelet isn‘t running or healthy.
merlon学习笔记
03-31 2042
k8s初始化报错：[kubelet-check] It seems like the kubelet isn't running or healthy. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: conne
initial timeout of 40s passed 怎么处理
05-14
"initial timeout of 40s passed" 意味着在一开始连接时等待40秒后仍未连接成功。这可能是由于网络连接不稳定或服务器繁忙导致的。以下是一些可能的解决方法： 1. 重试连接：尝试重新连接几次，看看是否能够成功建立连接。 2. 检查网络连接：检查网络连接是否正常，尤其是当你使用的是无线网络时。 3. 检查服务器状态：检查服务器是否正常运行，如果服务器负载过高，可能会导致连接超时。 4. 增加连接超时时间：如果连接超时时间太短，可以尝试增加连接超时时间。 如果以上方法都无法解决问题，可以尝试联系服务器管理员寻求帮助。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 9
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值