k8s Get http://127.0.0.1:10252/healthz: dial tcp 127.0.0.1:10252: connect: connection refused问题解决

安装完k8s集群之后很可能会出现一下情况：

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

出现这种情况是kube-controller-manager.yaml和kube-scheduler.yaml设置的默认端口是0，在文件中注释掉就可以了。(每台master节点都要执行操作)

1. 修改kube-scheduler.yaml文件

   cat  /etc/kubernetes/manifests/kube-scheduler.yaml
   apiVersion: v1
   kind: Pod
   metadata:
     creationTimestamp: null
     labels:
       component: kube-scheduler
       tier: control-plane
     name: kube-scheduler
     namespace: kube-system
   spec:
     containers:
     - command:
       - kube-scheduler
       - --authentication-kubeconfig=/etc/kubernetes/scheduler.conf
       - --authorization-kubeconfig=/etc/kubernetes/scheduler.conf
       - --bind-address=127.0.0.1
       - --kubeconfig=/etc/kubernetes/scheduler.conf
       - --leader-elect=true
   #    - --port=0 #注释掉
       image: registry.aliyuncs.com/google_containers/kube-scheduler:v1.21.0
       imagePullPolicy: IfNotPresent
       livenessProbe:
         failureThreshold: 8
         httpGet:
           host: 127.0.0.1
           path: /healthz
           port: 10259
           scheme: HTTPS
         initialDelaySeconds: 10
         periodSeconds: 10
         timeoutSeconds: 15
       name: kube-scheduler
       resources:
         requests:
           cpu: 100m
       startupProbe:
         failureThreshold: 24
         httpGet:
           host: 127.0.0.1
           path: /healthz
           port: 10259
           scheme: HTTPS
         initialDelaySeconds: 10
         periodSeconds: 10
         timeoutSeconds: 15
       volumeMounts:
       - mountPath: /etc/kubernetes/scheduler.conf
         name: kubeconfig
         readOnly: true
     hostNetwork: true
     priorityClassName: system-node-critical
     volumes:
     - hostPath:
         path: /etc/kubernetes/scheduler.conf
         type: FileOrCreate
       name: kubeconfig
   status: {}

2. 　　修改kube-controller-manager.yaml文件

   cat /etc/kubernetes/manifests/kube-controller-manager.yaml
   apiVersion: v1
   kind: Pod
   metadata:
     creationTimestamp: null
     labels:
       component: kube-controller-manager
       tier: control-plane
     name: kube-controller-manager
     namespace: kube-system
   spec:
     containers:
     - command:
       - kube-controller-manager
       - --allocate-node-cidrs=true
       - --authentication-kubeconfig=/etc/kubernetes/controller-manager.conf
       - --authorization-kubeconfig=/etc/kubernetes/controller-manager.conf
       - --bind-address=127.0.0.1
       - --client-ca-file=/etc/kubernetes/pki/ca.crt
       - --cluster-cidr=10.244.0.0/16
       - --cluster-name=kubernetes
       - --cluster-signing-cert-file=/etc/kubernetes/pki/ca.crt
       - --cluster-signing-key-file=/etc/kubernetes/pki/ca.key
       - --controllers=*,bootstrapsigner,tokencleaner
       - --kubeconfig=/etc/kubernetes/controller-manager.conf
       - --leader-elect=true
   #    - --port=0 #注释掉
       - --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt
       - --root-ca-file=/etc/kubernetes/pki/ca.crt
       - --service-account-private-key-file=/etc/kubernetes/pki/sa.key
       - --service-cluster-ip-range=10.96.0.0/12
       - --use-service-account-credentials=true
       image: registry.aliyuncs.com/google_containers/kube-controller-manager:v1.21.0
       imagePullPolicy: IfNotPresent
       livenessProbe:
         failureThreshold: 8
         httpGet:
           host: 127.0.0.1
           path: /healthz
           port: 10257
           scheme: HTTPS
         initialDelaySeconds: 10
         periodSeconds: 10
         timeoutSeconds: 15
       name: kube-controller-manager
       resources:
         requests:
           cpu: 200m
       startupProbe:
         failureThreshold: 24
         httpGet:
           host: 127.0.0.1
           path: /healthz
           port: 10257
           scheme: HTTPS
         initialDelaySeconds: 10
         periodSeconds: 10
         timeoutSeconds: 15
       volumeMounts:
       - mountPath: /etc/ssl/certs
         name: ca-certs
         readOnly: true
       - mountPath: /etc/pki
         name: etc-pki
         readOnly: true
       - mountPath: /usr/libexec/kubernetes/kubelet-plugins/volume/exec
         name: flexvolume-dir
       - mountPath: /etc/kubernetes/pki
         name: k8s-certs
         readOnly: true
       - mountPath: /etc/kubernetes/controller-manager.conf
         name: kubeconfig
         readOnly: true
     hostNetwork: true
     priorityClassName: system-node-critical
     volumes:
     - hostPath:
         path: /etc/ssl/certs
         type: DirectoryOrCreate
       name: ca-certs
     - hostPath:
         path: /etc/pki
         type: DirectoryOrCreate
       name: etc-pki
     - hostPath:
         path: /usr/libexec/kubernetes/kubelet-plugins/volume/exec
         type: DirectoryOrCreate
       name: flexvolume-dir
     - hostPath:
         path: /etc/kubernetes/pki
         type: DirectoryOrCreate
       name: k8s-certs
     - hostPath:
         path: /etc/kubernetes/controller-manager.conf
         type: FileOrCreate
       name: kubeconfig
   status: {}

3. 重启 master 的 kubele

   systemctl restart kubelet.service

4. 再次查看状态　

   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"}