暂无图片
暂无图片
暂无图片
暂无图片
暂无图片

K8s 集群Controller-manager和Scheduler 状态错误

DevOps架构实战 2021-10-13
2631

点击蓝色“DevOps架构实战”关注我哟

分享到“朋友圈”,每天上午 07:30,干货推送!

[root@master ~]# kubectl get cs

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

在文件中注释掉默认端口0

[root@master ~]# vim 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.20.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

[root@master ~]# vim 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

[root@master ~]# systemctl restart kubelet

[root@master ~]# kubectl get cs

Warning: v1 ComponentStatus is deprecated in v1.19+

NAME        STATUS    MESSAGE        ERROR

scheduler            Healthy   ok                  

controller-manager   Healthy   ok                  

etcd-0               Healthy   {"health":"true"}   

----------------------end---------------------

推荐阅读:

小米监控Open-Falcon

日志系统ELK+Filebeat集群部署

又来需求啦--批量部署50台mysql

Kubernetes持久化存储NFS

带你搞懂K8s部署Mysql8.0

文章转载自DevOps架构实战,如果涉嫌侵权,请发送邮件至:contact@modb.pro进行举报,并提供相关证据,一经查实,墨天轮将立刻删除相关内容。

评论