Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.

因为标题放不下完整的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..

这里提供一个解决方法:

１．首先去查看下你的:  /etc/systemd/system/kubelet.service.d
路径下有没有一个文件:10-kubeadm.conf．
如果没有的话，你就把以下内容复制一下(注意我的k8s版本是v1.17.3，如果别的版本修改完以后，无效的话，请另寻它法）

# Note: This dropin only works with kubeadm and kubelet v1.11+
[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"
# This is a file that "kubeadm init" and "kubeadm join" generates at runtime, populating the KUBELET_KUBEADM_ARGS variable dynamically
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. Preferably, the user should use
# the .NodeRegistration.KubeletExtraArgs object in the configuration files instead. KUBELET_EXTRA_ARGS should be sourced from this file.
EnvironmentFile=-/etc/default/kubelet
ExecStart=
ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS

如果存在这个文件的话，就在这个文件中添加一句:

Environment="KUBELET_SYSTEM_PODS_ARGS=--pod-manifest-path=/etc/kubernetes/manifests --allow-privileged=true --fail-swap-on=false"

重新启动kubelet.service1.systemctl daemon reload2.systemctl restart kubelet.service

最终解决初始化中出现的上述的问题，希望你们也可以解决问题．

Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.相关推荐

K8S报错：controller-manager Unhealthy Get http://127.0.0.1:10252/healthz: dial tcp 127.0.0.1:10252
controller-manager Unhealthy Get "http://127.0.0.1:10252/healthz": dial tcp 127.0.0.1:1025 ...
单机启动schedule报错：Get http://127.0.0.1:10251/healthz: dial tcp 127.0.0.1:10251: connect: connection ref
方案: 将scheduler启动项中的KUBE_SCHEDULER_ARGS加上值127.0.0.1即可
scheduler Unhealthy Get “http://127.0.0.1:10251/healthz“: dial tcp 127.0.0.1:10251: connect: connec
1.使用kubectl get cs检查k8s组件状态时发现scheduler unhealthy. 2.通过netstat -lntp|grep 10251和systemctl status kub ...
dial tcp [::1]:10248: connect: connection refused
k8s加入节点时报错 [root@node2 ~]# kubeadm join 192.168.75.140:6443 --token ap25bk.sodr97gp1w8p01xv --discov ...
K8S组件scheduler和controller-manager报错：dial tcp 127.0.0.1:10252: connect: connection refused
组件scheduler和controller-manager报错:dial tcp 127.0.0.1:10252: connect: connection refused 使用工具kubeadm安装 ...
harbor 报错：dial tcp 127.0.0.1:1514: connect: connection refused 解决
现象:harbor 部署成功后,慢慢"死亡",以下用图展示拉起的镜像慢慢死亡的过程图一:部署成功图二:容器nginx,一直restarting,陷入无限重启中图三:因为harb ...
dial tcp 10.96.0.1:443: getsockopt: no route to host --- kubernetes（k8s）DNS 服务反复重启
kubernetes(k8s)DNS 服务反复重启解决: k8s.io/dns/pkg/dns/dns.go:150: Failed to list *v1.Service: Get https:// ...
Tiller pods can‘t connect to k8s apiserver，dial tcp 10.254.0.1:443: no route to host
1. 问题使用helm list查看本地安装应用时,报错 # helm listError: Get https://10.254.0.1:443/api/v1/namespaces/kube-sy ...
解决：consumer: Cannot connect to amqp://admin:**@127.0.0.1:5672//: [Errno 111] Connection refused.
为了避免大家机毁人亡,徒耗精力搜索到一堆没用的重复旧文,我决定写下这篇关于docker容器化的celery 无法连接rabbitmq的文章,以增强互联网的技术氛围和工程师的原创精神 worker_1 ...

Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.

Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.相关推荐

最新文章

热门文章