解决K8s安装中节点初始化时 [kubelet-check] The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘ 问题.

最新推荐文章于 2024-01-12 09:39:50 发布
最新推荐文章于 2024-01-12 09:39:50 发布
阅读量6.3k 收藏 23
点赞数 10
文章标签： kubernetes kubelet linux
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_51589360/article/details/128290237
版权

问题描述：
安装K8s时，在节点初始化过程中出现[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: connection refused.报错。

#在安装K8s初始化主节点过程中，出现如下报错：
queena@queena-Lenovo:~$ sudo kubeadm init --apiserver-advertise-address=192.168.31.245 --pod-network-cidr=10.244.0.0/16  --kubernetes-version=v1.22.3
[init] Using Kubernetes version: v1.22.3
[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 [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local queena-lenovo] and IPs [10.96.0.1 192.168.31.245]
[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 [localhost queena-lenovo] and IPs [192.168.31.245 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [localhost queena-lenovo] and IPs [192.168.31.245 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.
[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: connection refused.
[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: connection refused.

......
    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

#根据上述官方提供的方法进行检查。
queena@queena-Lenovo:~$ systemctl status kubelet
● kubelet.service - kubelet: The Kubernetes Node Agent
   Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2022-12-12 16:53:20 CST; 8s ago
     Docs: https://kubernetes.io/docs/home/
  Process: 5208 ExecStart=/usr/bin/kubelet (code=exited, status=1/FAILURE)
 Main PID: 5208 (code=exited, status=1/FAILURE)
 
queena@queena-Lenovo:~$ journalctl -xeu kubelet
-- 
-- Automatic restarting of the unit kubelet.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
12月 12 16:54:21 queena-Lenovo systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
-- Subject: kubelet.service 单元已结束停止操作
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- kubelet.service 单元已结束停止操作。
12月 12 16:54:21 queena-Lenovo systemd[1]: Started kubelet: The Kubernetes Node Agent.
-- Subject: kubelet.service 单元已结束启动
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- kubelet.service 单元已结束启动。
-- 
-- 启动结果为“RESULT”。
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.657289    6039 server.go:440] "Kubelet version" kubeletVersion="v1.22.3"
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.657859    6039 server.go:600] "Standalone mode, no API client"
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.737923    6039 server.go:488] "No api server defined - no events will be sent to API server"
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.737948    6039 server.go:687] "--cgroups-per-qos enabled, but --cgroup-root was not specified.  d
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.738162    6039 container_manager_linux.go:280] "Container manager verified user specified cgroup-
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.738244    6039 container_manager_linux.go:285] "Creating Container Manager object based on Node C
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.738337    6039 topology_manager.go:133] "Creating topology manager with policy per scope" topolog
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.738350    6039 container_manager_linux.go:320] "Creating device plugin manager" devicePluginEnabl
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.738378    6039 state_mem.go:36] "Initialized new in-memory state store"
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.738420    6039 kubelet.go:314] "Using dockershim is deprecated, please consider using a full-fled
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.738454    6039 client.go:78] "Connecting to docker on the dockerEndpoint" endpoint="unix:///var/r
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.738468    6039 client.go:97] "Start docker client with request timeout" timeout="2m0s"
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.744849    6039 docker_service.go:566] "Hairpin mode is set but kubenet is not enabled, falling ba
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.744875    6039 docker_service.go:242] "Hairpin mode is set" hairpinMode=hairpin-veth
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.744966    6039 cni.go:239] "Unable to update cni config" err="no networks found in /etc/cni/net.d
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.748677    6039 docker_service.go:257] "Docker cri networking managed by the network plugin" netwo
12月 12 16:54:21 queena-Lenovo kubelet[6039]: I1212 16:54:21.756004    6039 docker_service.go:264] "Docker Info" dockerInfo=&{ID:H56N:KEB3:V52D:LJPL:GLGW:XBHY
12月 12 16:54:21 queena-Lenovo kubelet[6039]: E1212 16:54:21.756040    6039 server.go:294] "Failed to run kubelet" err="failed to run Kubelet: misconfiguratio
12月 12 16:54:21 queena-Lenovo systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
12月 12 16:54:21 queena-Lenovo systemd[1]: kubelet.service: Failed with result 'exit-code'.

解决方法：

1、驱动问题，即docker的驱动与kubelet 驱动不一致

#查看docker驱动.
queena@queena-Lenovo:~$ docker info | grep Cgroup
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
WARNING: No swap limit support

#查看kubelet驱动.
queena@queena-Lenovo:~$ sudo cat /var/lib/kubelet/config.yaml | grep cgroup
cgroupDriver: systemd

#修改docker驱动，查看/etc/docker/daemon.json文件，没有的话，手动创建，添加以下内容:
queena@queena-Lenovo:~$ vim /etc/docker/daemon.json
#在该文件中加入，   "exec-opts": ["native.cgroupdriver=systemd"]
{
  "registry-mirrors": ["https://dpxn2pal.mirror.aliyuncs.com"],
  "exec-opts": [ "native.cgroupdriver=systemd" ]
}

#重启docker 
queena@queena-Lenovo:~$ systemctl daemon-reload
queena@queena-Lenovo:~$ systemctl restart docker
#重启kubelet
queena@queena-Lenovo:~$ systemctl restart kubelet
queena@queena-Lenovo:~$ sudo kubeadm reset  #此处重置，没关系，反正原来的也起不来.

#下面这两行用来验证cgroupdriver 修改生效，都得出systemd.
queena@queena-Lenovo:~$ docker info -f {{.CgroupDriver}}
systemd
queena@queena-Lenovo:~$ docker info | grep -i cgroup
 Cgroup Driver: systemd
 Cgroup Version: 1
WARNING: No swap limit support

#再次执行K8s初始化主节点，即可成功.
queena@queena-Lenovo:~$ sudo kubeadm init --apiserver-advertise-address=192.168.31.245 --pod-network-cidr=10.244.0.0/16  --kubernetes-version=v1.22.3
...
Your Kubernetes control-plane has initialized successfully!
...

2、10-kubeadm.conf配置文件不存在

（1）先去查看: /etc/systemd/system/kubelet.service.d下是否有10-kubeadm.conf．如果没有，则需要创建这个文件，并输入如下内容：
queena@queena-Lenovo:/etc/systemd/system/kubelet.service.d$ sudo vim 10-kubeadm.conf
[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf"
Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml"
EnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env
# This is a file that the user can use for overrides of the kubelet args as a last resort. 
EnvironmentFile=-/etc/default/kubelet
ExecStart=
ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS
（2）如果有这个文件，则在文件中加入以下代码：
Environment="KUBELET_SYSTEM_PODS_ARGS=--pod-manifest-path=/etc/kubernetes/manifests --allow-privileged=true --fail-swap-on=false"
（3）重新启动kubelet.service
queena@queena-Lenovo:/etc/systemd/system/kubelet.service.d$ systemctl daemon-reload
queena@queena-Lenovo:/etc/systemd/system/kubelet.service.d$ systemctl restart kubelet.service
queena@queena-Lenovo:/etc/systemd/system/kubelet.service.d$ sudo kubeadm reset
...
queena@queena-Lenovo:/etc/systemd/system/kubelet.service.d$ sudo kubeadm init --apiserver-advertise-address=192.168.31.245 --pod-network-cidr=10.244.0.0/16  --kubernetes-version=v1.22.3
...
Your Kubernetes control-plane has initialized successfully!
...

至此，问题得以解决！

鹰KING
关注
  • 10
    点赞
  • 踩
  • 23
    收藏
    觉得还不错? 一键收藏
  • 2
    评论
K8s（十五）：节点kubeadm join报错 The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘
✨ 欢迎来到【Seal ^_^ 的CSDN博客】！这里是我记录技术心得、分享经验的地方。✨
04-10 1万+
🔴 K8s（十五）：节点kubeadm join报错 The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘
报错The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘ failed with error: Get “http://l
最新发布
之度的博客
01-30 565
安装1.22.2版本的k8s时候，初始化报错The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz":。docker的cgroup驱动程序默认设置为system。默认情况下Kubernetes cgroup为systemd，我们需要更改Docker cgroup驱动。2）重新更换docker驱动。1）重新重置k8s,
利用kubeadm搭建测试kubernetes集群
hanlaipeng的博客
10-21 1577
使用工具     https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ kubeadm简介：     kubeadm是kubernetes自带的快速搭建kubernetes集群的工具，方便快捷，并且很好的支持自定义搭建。它在开源社区还是很有活力的，虽然目前kubeadm目前还不能用于生产环境，但是伴随着kub...
The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘ failed with error: Get “http://loc
King config
12-29 1万+
问题: 初始化K8S master时报错 The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp [::1]:10248: connect: connection refused. 问题分析： 之前我的Docker是用yum安装的，docker的cgroup驱动程序默认设置为systemd。默认情况
[kubelet-check] The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘ failed with error
weixin_44197719的博客
06-16 1992
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error
kubeadm相关指令出现kubeadm-config无法找到的问题解决
为梦想奋斗
07-03 1428
问题的现象是凡是执行kubeadm相关的指令，如kubeadm upgrade plan等，都会出现类似以下的错误
【问题解决】[kubelet-check] The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘ failed wite
热门推荐
看，未来的博客
07-01 1万+
报错：[kubelet-check] The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz’ failed with error: Get “http://localhost:10248/healthz”: dial tcp [::1]:10248: connect: connection refused.原因：执行初始化安装命令 kubeadm init … 报错故障： [etcd] Creating static Pod man
The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘ failed with error: Get “ht........
mo_sss的博客
01-12 1052
每个人都有惰性，但不断学习是好好生活的根本，共勉！
解决：k8s[kubelet-check] The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz’ failed with
qq_29349143的博客
10-20 1万+
解决：k8s[kubelet-check] The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz’ failed with error: Get “http://localhost:10248/healthz”: dial tcp [::1]:10248: connect: connection refused 搭建k8s出现的问题记录 [kubelet-check] The HTTP call equal to ‘curl -sS
[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
node-deep-equal：节点的assert.deepEqual算法
02-04
深平等 Node的assert.deepEqual() algorithm作为独立模块。 这个模块比在try/catch包装assert.deepEqual()约。 例 var equal = require ( 'deep-equal' ) ; console . dir ( [ equal ( { a : [ 2 , 3 ] , b : [ 4 ] } , { a : [ 2 , 3 ] , b : [ 4 ] } ) , equal ( { x : 5 , y : [ 6 ] } , { x : 5
runasil_V0_0_0_1.zip_C/C++_
08-12
http://blog.didierstevens.com/2010/12/01/runasil/The following command launches notepad.exe with a low integrity levelrunasil.exe notepad.exe test.txtTo automatically launch notepad via runasil.exeHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\notepad.exeand create a value debugger equal to "runasil.exe -d" (don t forget option -d).You can also specify the integrity level via an option:-l for low-m for medium-h for high-s for systemBy defaultDon t fo
matlab坐标轴刻度代码-poisson-surface-reconstruction:使用MATLABMEX-File绑定的http://
05-27
matlab坐标轴校准代码泊松侦察 使用MATLAB MEX-File绑定的CMake构建 建造 cmake -H. -Bbuild -DCMAKE_BUILD_TYPE=Release make -j4 -Cbuild 用法 [faces, vertices] = poissonRecon(points, normals, depth, fullDepth, scale, samplesPerNode, cgDepth); 例子 [x, y, z] = sphere(15); pts = [x(:), y(:), z(:)]; normals = normalize(-pts); figure; drawPoint3d(pts); drawEdge3d([pts, pts+normalize(normals)*0.15]); axis equal; grid on; [faces, vertices] = poissonRecon(pts, normals, 3); figure; trimesh(faces, vertices(:,1), vertices(:,2), vertic
unist-util-is:检查节点是否通过测试的实用程序
03-07
Unist-util-is 实用程序，用于检查节点是否通过测试。 安装 ： npm install unist-util-is 使用 var is = require ( 'unist-util-is' ) var node = { type : 'strong' } var parent = { type : 'paragraph' , children : [ node ] } function test ( node , n ) { return n === 5 } is ( ) // => false is ( { children : [ ] } ) // => false is ( node ) // => true is ( node , 'strong' ) // => true is ( node , 'emphasis' ) // => false is (
async-htm-to-string:将带有htm标签的模板异步呈现为字符串
03-18
异步htm到字符串 将带有标签的模板异步呈现为字符串。 用法 简单的 yarn add async-htm-to-string const { html , renderToString } = require ( 'async-htm-to-string' ) ; const customTag = ( { prefix } , children ) => html ` < div> ${ prefix } - ${ children } </ div> ` ; const dynamicContent = 'bar' ; // Will equal "<div>foo-bar</div> const result = await renderToString ( html ` < ${ customTag } prefix ="foo" > ${ dynamicContent }
fast-deep-equal:最快的深度相等检查，支持 Date、RegExp 和 ES6 Map、Set 和类型数组
08-04
安装 npm install fast-deep-equal 特征 兼容 ES5 适用于 node.js (8+) 和浏览器 (IE9+) 按值检查 Date 和 RegExp 对象的相等性。 ES6 equal ( require('fast-deep-equal/es6') ) 也支持： 地图 套 类型化数组 ...
Leetcode-Challenge:所有Leetcode解决方案，其视频均在频道中
04-18
Leetcode挑战 2021年4月Leetcoding...https://leetcode.com/problems/minimum-operations-to-make-array-equal/ https://youtu.be/9aGx9hoIBjI https://github.com/Algorithms-Made-Easy/Leetcode-Challenge/blob/
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz'
11-02
该报错是由于kubelet无法连接到本地的10248端口导致的。解决方法是重启docker并重新初始化kubeadm。具体步骤如下： ``` # 添加以下内容 vim /etc/docker/daemon.json { "exec-opts": ["native.cgroupdriver=systemd"] } # 重启docker systemctl restart docker # 重新初始化 kubeadm reset # 先重置 kubeadm init \ --apiserver-advertise-address=192.168.42.122 \ --image-repository registry.aliyuncs.com/google_containers \ --kubernetes-version v1.22.2 \ --service-cidr=10.96.0.0/12 \ --pod-network-cidr=10.244.0.0/16 \ --ignore-preflight-errors=all ```

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值