k8s系列：node节点 kubeadmin init报错http://localhost:10248/healthz‘ failed

最新推荐文章于 2024-07-30 16:53:42 发布
原创 最新推荐文章于 2024-07-30 16:53:42 发布 · 437 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#kubernetes #java #容器

本文档主要描述了在k8s环境中，遇到node节点kubeadmin init失败的问题，报错信息为'http://localhost:10248/healthz' failed。解决方法包括指定cgroupdriver为systemd，并通过重启docker服务来应用更改。

目录

现象

指定cgroupdriver

重启docker 

现象

node节点 kubeadmin init报错http://localhost:10248/healthz‘ failed

指定cgroupdriver

cat > /etc/docker/daemon.json <<EOF
{"exec-opts": ["native.cgroupdriver=systemd"]}
EOF

重启docker 


systemctl restart docker

K8s（十五）：节点kubeadm join报错 The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘
✨ 欢迎来到【Seal ^_^ 的优快云博客】！✨
04-10 1万+
🔴 K8s（十五）：节点kubeadm join报错 The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘
【ubutnu18.04】k8s 部署4: worker节点配置1.31.0和containerd 1.7.20
突围
08-16 615
1.31.0并init成功
k8s kubeadmin init报错http://localhost:10248/healthz‘ failed
IPVPN的博客
04-14 2379
Failed to run kubelet" err="failed to run Kubelet: misconfiguration: kubelet cgroup driver: \"systemd\" is different from docker cgroup driver: \"cgroupfs\ The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error:
K8S:master添加node节点显示本地访问10248端口被拒绝
songci3756的博客
07-13 1758
在添加node节点时出现了报错： 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 refusewom。1、首先，我们都知道，在K8S中组件中，端口为10248的组件为kubelet，果然，kubelet是没有启动起来，
[K8S] kubeadm init部署K8S
皮卡丘在充电
08-08 782
官方文档 ->https://kubernetes.io/zh/docs/home/ @Kubernetes 是什么？ https://v1-21.docs.kubernetes.io/zh/docs/concepts/overview/what-is-kubernetes/ 访问和工具层 Web控制台、RESTful API、日志、监控、CI/CD PaaS服务层 统一服务平台 容器编排层 K8S 容器引擎层 Docker IaaS基础设施层 提供.
node启动服务报错Node.js Error: Cannot find module express
dibengshao7358的博客
03-10 328
在node文件夹中(M:\express-test),执行 npm install express 在使用npm安装express时，报npm WARN saveError ENOENT: no such file or directory, open 'M:\express-test\package.json'错误, 和下面错误一样: 错误原因：项目没有package.js...
成功解决： Get “http://localhost:10248/healthz“: dial tcp [::1]:10248: connect: connection refused.
未来社会二十年发展的核心技术趋势由ABCD四个字母组成，分别是AI（人工智能）、BlockChain（区块链）、Cloud（云）、和Data（大数据）每一次进步都有新的认知和感触
05-06 4593
我在部署k8s集群使用kubeadm初始化报报错，成功解决： Get "http://localhost:10248/healthz": dial tcp [::1]:10248: connect: connection refused.
k8s1.24.0版本加入节点报错
weixin_43156511的博客
05-12 1876
[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 环境:Centos7安装生产环境可用的K8S集群图文教程指南
极客星云-优快云博客
12-15 2081
本文分享了在Centos7系统上搭建生产可用K8S集群的详细教程。
k8s apiserver的代理健康检测问题
chuiyanyou9920的博客
06-12 1113
apiserver前面如果有lvs做高可用，lvs对apiserver做健康检测要注意不能使用tcp check,否则会触发报错 I0602 06:16:23.897813 1 log.go:172] http: TLS handshake error from x.x.x.x:4...
解决k8s集群初始化过程中报错HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘ failed with
shnu_cdk的博客
02-23 667
报错如图所示，在集群master初始化k8s时，出现上述错误，本来以为是docker没有配置systemd，但是发现配置了，考虑如下解决手段。再次初始化，发现不再报错。
kubeadm init 出现failed with error: Get “http://localhost:10248/healthz“:
chililopp的博客
07-30 354
安装k8s主节点的时候遇见一下问题：解决方法： 加上：, "exec-opts": ["native.cgroupdriver=systemd"]重启docker 然后reset一下： 重新执行kubeadm init，结果为success！
安装 minikube 后使用 kubeadm init 报错 http://localhost:10248/healthz‘ failed with error connection refu问题
锄禾日当午，啥都不靠谱；闲来没事做，不如写博客。
08-12 662
首先安装的是 minikube，然后 minikube 还没卸载清理干净就使用 kubeadm init 来想要安装正式一点集群环境，结果前面各种步骤都没有问题，就是在启动 kubectl 的时候一直报如下错误。
k8s初始化过程中，failed with error: Get “http://localhost:10248/healthz“
稻草人
12-24 5918
k8s init 异常 failed with error: Get "http://localhost:10248/healthz"
kubeadm init时出错
weixin_54225397的博客
05-24 642
提示拉取 registry.aliyuncs.com/google_containers/coredns:v1.8.0 镜像失败。然后执行 Kubernetes init。在执行init之前先执行。
【已解决】k8s部署遇到的问题记录(1)---kubeadm init 失败
weixin_49064876的博客
01-10 7188
而且[ERROR FileAvailable–etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists提示了相关的yaml文件已存在。2.删除相关配置文件（终端提示有kubeadm reset 执行后不会删除$HOME/.kube文件，需要手动删除）说明了已有kubeadm在运行中，需要关闭当前已运行的kubeadm。1.重启kubeadm。
小白初始化项目时，node报错。从哪些方面来分析
webA_zi的博客
07-30 171
初始化
kubeadm init初始化报错
Didier__的博客
06-10 6065
kubeadm init 初始化异常报错处理
解决K8s安装中节点初始化时 [kubelet-check] The HTTP call equal to ‘curl -sSL http://localhost:10248/healthz‘ 问题.
weixin_51589360的博客
12-12 9241
安装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.报错。
guyue@k8s-worker01:~$ # 停止所有服务 sudo systemctl stop kubelet sudo systemctl stop cri-docker.service sudo systemctl stop containerd sudo systemctl stop docker # 彻底清理 kubeadm 配置 sudo kubeadm reset --force --cri-socket unix:///var/run/cri-dockerd.sock # 手动删除所有残留配置 sudo rm -rf /etc/kubernetes/* sudo rm -rf /var/lib/kubelet/* sudo rm -rf /var/lib/etcd/* sudo rm -rf /etc/cni/net.d/* # 清理 iptables 规则 sudo iptables -F sudo iptables -t nat -F sudo iptables -t mangle -F sudo iptables -t raw -F sudo systemctl daemon-reload default | xargs -r sudo ip netns delete Stopping 'docker.service', but its triggering units are still active: docker.socket [preflight] Running pre-flight checks W1202 13:26:55.625312 40333 removeetcdmember.go:106] [reset] No kubeadm config, using etcd pod spec to get data directory [reset] Deleted contents of the etcd data directory: /var/lib/etcd [reset] Stopping the kubelet service [reset] Unmounting mounted directories in "/var/lib/kubelet" W1202 13:26:55.768797 40333 cleanupnode.go:99] [reset] Failed to remove containers: output: E1202 13:26:55.763484 40339 remote_runtime.go:277] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused\"" filter="&PodSandboxFilter{Id:,State:nil,LabelSelector:map[string]string{},}" time="2025-12-02T13:26:55+08:00" level=fatal msg="listing pod sandboxes: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/cri-dockerd.sock: connect: connection refused\"" , error: exit status 1 [reset] Deleting contents of directories: [/etc/kubernetes/manifests /var/lib/kubelet /etc/kubernetes/pki] [reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf] The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d The reset process does not reset or clean up iptables rules or IPVS tables. If you wish to reset iptables, you must do so manually by using the "iptables" command. If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar) to reset your system's IPVS tables. The reset process does not clean your kubeconfig files and you must remove them manually. Please, check the contents of the $HOME/.kube/config file. guyue@k8s-worker01:~$ # 创建专用的 kubelet 配置目录 sudo mkdir -p /etc/systemd/system/kubelet.service.d/ # 创建正确的配置文件（使用 .conf 后缀） sudo tee /etc/systemd/system/kubelet.service.d/10-kubeadm.conf <<EOF [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" Environment="KUBELET_EXTRA_ARGS=--container-runtime-endpoint=unix:///var/run/cri-dockerd.sock --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.9 --v=2" EOF # 重新加载 systemd 配置 sudo systemctl daemon-reload # 验证配置 sudo systemctl cat kubelet [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" Environment="KUBELET_EXTRA_ARGS=--container-runtime-endpoint=unix:///var/run/cri-dockerd.sock --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.9 --v=2" # /usr/lib/systemd/system/kubelet.service [Unit] Description=kubelet: The Kubernetes Node Agent Documentation=https://kubernetes.io/docs/home/ Wants=network-online.target After=network-online.target [Service] ExecStart=/usr/bin/kubelet Restart=always StartLimitInterval=0 RestartSec=10 [Install] WantedBy=multi-user.target # /etc/systemd/system/kubelet.service.d/0-containerd.conf [Service] Environment="KUBELET_EXTRA_ARGS=--container-runtime-endpoint=unix:///var/run/cri> lines 1-20 [4]+ 已停止 sudo systemctl cat kubelet guyue@k8s-worker01:~$ # 创建或覆盖 /etc/default/kubelet（最高优先级配置） echo 'KUBELET_EXTRA_ARGS="--container-runtime-endpoint=unix:///var/run/cri-dockerd.sock --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.9"' | sudo tee /etc/default/kubelet # 启动 cri-dockerd sudo systemctl start cri-docker.service sudo systemctl enable cri-docker.service # 验证 CRI 连接 sudo crictl --runtime-endpoint unix:///var/run/cri-dockerd.sock version sudo crictl --runtime-endpoint unix:///var/run/cri-dockerd.sock info KUBELET_EXTRA_ARGS="--container-runtime-endpoint=unix:///var/run/cri-dockerd.sock --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.9" Version: 0.1.0 RuntimeName: docker RuntimeVersion: 29.0.0 RuntimeApiVersion: v1 { "status": { "conditions": [ { "type": "RuntimeReady", "status": true, "reason": "", "message": "" }, { "type": "NetworkReady", "status": false, "reason": "NetworkPluginNotReady", "message": "docker: network plugin is not ready: cni config uninitialized" } ] }, "config": { "sandboxImage": "registry.aliyuncs.com/google_containers/pause:3.10.1" } } guyue@k8s-worker01:~$ # 启动 kubelet sudo systemctl start kubelet sudo systemctl enable kubelet # 监控日志（在新终端中运行） sudo journalctl -u kubelet -f --since "now" 12月 02 13:27:38 k8s-worker01 kubelet[40971]: I1202 13:27:38.069109 40971 server.go:467] "Kubelet version" kubeletVersion="v1.28.2" 12月 02 13:27:38 k8s-worker01 kubelet[40971]: I1202 13:27:38.069243 40971 server.go:469] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK="" 12月 02 13:27:38 k8s-worker01 kubelet[40971]: I1202 13:27:38.069532 40971 server.go:630] "Standalone mode, no API client" 12月 02 13:27:38 k8s-worker01 kubelet[40971]: E1202 13:27:38.073889 40971 run.go:74] "command failed" err="failed to run Kubelet: validate service connection: validate CRI v1 runtime API for endpoint \"unix:///run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService" 12月 02 13:27:38 k8s-worker01 systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE 12月 02 13:27:38 k8s-worker01 systemd[1]: kubelet.service: Failed with result 'exit-code'. 12月 02 13:27:38 k8s-worker01 systemd[1]: kubelet.service: Consumed 1.915s CPU time, 7.0M memory peak, 0B memory swap peak. 12月 02 13:27:48 k8s-worker01 systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 42. 12月 02 13:27:48 k8s-worker01 systemd[1]: Started kubelet.service - kubelet: The Kubernetes Node Agent. 12月 02 13:27:48 k8s-worker01 kubelet[41091]: I1202 13:27:48.478732 41091 server.go:467] "Kubelet version" kubeletVersion="v1.28.2" 12月 02 13:27:48 k8s-worker01 kubelet[41091]: I1202 13:27:48.478879 41091 server.go:469] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK="" 12月 02 13:27:48 k8s-worker01 kubelet[41091]: I1202 13:27:48.479651 41091 server.go:630] "Standalone mode, no API client" 12月 02 13:27:48 k8s-worker01 kubelet[41091]: E1202 13:27:48.485767 41091 run.go:74] "command failed" err="failed to run Kubelet: validate service connection: validate CRI v1 runtime API for endpoint \"unix:///run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService" 12月 02 13:27:48 k8s-worker01 systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE 12月 02 13:27:48 k8s-worker01 systemd[1]: kubelet.service: Failed with result 'exit-code'. ^Z [5]+ 已停止 sudo journalctl -u kubelet -f --since "now" guyue@k8s-worker01:~$ # 在确认 kubelet 正常运行后（看到类似 "Starting to listen on 0.0.0.0:10250" 的日志） sudo kubeadm join 192.168.130.129:6443 \ --token h0epjb.94zz1xhekvf7nfzx \ --discovery-token-ca-cert-hash sha256:a7760aa4d05b6bf0af6be91267c86417999c998318bfe4a8afcb62b757b8f808 \ --cri-socket unix:///var/run/cri-dockerd.sock \ --ignore-preflight-errors=all [preflight] Running pre-flight checks [preflight] Reading configuration from the cluster... [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml' [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 kubelet [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap... [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. [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.
最新发布
12-03
我们正在解决用户在重置kubeadm配置并清理残留后，kubelet无法正常启动以及...curl -sSL "http://localhost:10248/healthz" # 在 Node 节点执行 # 查看容器运行时状态 sudo crictl pods # 使用 cri-dockerd 时 ```
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

NIO4444

如果对您有帮助，欢迎打赏支持！

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值