K8S - Shooting Trouble

Richard123m

已于 2022-08-12 09:40:35 修改

阅读量531

点赞数

分类专栏： K8S 文章标签：服务器运维 kubernetes

于 2022-08-12 09:39:46 首次发布

本文链接：https://blog.youkuaiyun.com/c123m/article/details/126297521

版权

K8S 专栏收录该内容

3 篇文章

订阅专栏

该文章记录自己在学习使用K8S过程，遇到过的问题与解决方法，与大家分享之。

1. Get "http://127.0.0.1:10252/healthz": dial tcp 127.0.0.1:10252: connect: connection refused

现象

[root@t20 ~]# kubectl get cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS      MESSAGE                                                                                       ERROR
controller-manager   Unhealthy   Get "http://127.0.0.1:10252/healthz": dial tcp 127.0.0.1:10252: connect: connection refused   
scheduler            Unhealthy   Get "http://127.0.0.1:10251/healthz": dial tcp 127.0.0.1:10251: connect: connection refused   
etcd-0               Healthy     {"health":"true"}

解决: 在每台master节点上进行以下操作

[root@t20 ~]# cat  /etc/kubernetes/manifests/kube-scheduler.yaml 
...
16     - --bind-address=127.0.0.1
17     - --kubeconfig=/etc/kubernetes/scheduler.conf
18     - --leader-elect=true
19   #  - --port=0    # 注释掉该行


[root@t20 ~]# cat /etc/kubernetes/manifests/kube-controller-manager.yaml 
...
24     - --kubeconfig=/etc/kubernetes/controller-manager.conf
25     - --leader-elect=true
26  #   - --port=0   # 注释掉该行


[root@t20 ~]# systemctl restart kubelet

查看:

[root@t20 ~]# kubectl get cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME                 STATUS    MESSAGE             ERROR
controller-manager   Healthy   ok                  
scheduler            Healthy   ok                  
etcd-0               Healthy   {"health":"true"}