请稍等 ...
×

采纳答案成功!

向帮助你的同学说点啥吧!感谢那些助人为乐的人

主节点未加入集群

二进制部署,三主二从,集群部署后,
三个主节点查看nodes信息,都只能看到二个从节点信息,请问是哪里的问题
图片描述

正在回答 回答被采纳积分+3

插入代码

3回答

刘果国 2022-08-10 09:35:46

没问题的,集群正常。主节点默认是不以worker的角色加入集群的。要想主节点也加入需要在主节点也部署kubelet等组件,跟worker节点的流程一样

                                                                               
translator
                               
                                                       Double-click                                                    
                               
                                                       Select to translate                                                    
           
0 回复 有任何疑惑可以回复我~
提问者 慕前端304893 2022-08-09 17:47:03

老师,集群状态是失败的

[root@node-1 ~]# 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   Healthy     ok                                                                                            

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

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

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


                                                                         

[root@node-1 ~]# service kube-controller-manager status

Redirecting to /bin/systemctl status kube-controller-manager.service

● kube-controller-manager.service - Kubernetes Controller Manager

   Loaded: loaded (/etc/systemd/system/kube-controller-manager.service; enabled; vendor preset: disabled)

   Active: active (running) since Tue 2022-08-09 14:02:57 CST; 3h 40min ago

     Docs: https://github.com/kubernetes/kubernetes

 Main PID: 15762 (kube-controller)

   CGroup: /system.slice/kube-controller-manager.service

           └─15762 /usr/local/bin/kube-controller-manager --bind-address=0.0.0.0 --cluster-cidr=10.200.0.0/16 --cluster-name=kubernetes --cluster-signing-cert-file=/etc/kubernetes/ssl/ca.pem --cluster-signing-key-file=/etc/kuberne...


Aug 09 14:02:58 node-1 kube-controller-manager[15762]: I0809 14:02:58.001579   15762 flags.go:59] FLAG: --volume-host-cidr-denylist="[]"

Aug 09 14:02:58 node-1 kube-controller-manager[15762]: I0809 14:02:58.484634   15762 serving.go:331] Generated self-signed cert in-memory

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: W0809 14:02:59.071659   15762 authentication.go:303] No authentication-kubeconfig provided in order to lookup client-ca-file in configmap/extension-apiserver-au...ion won't work.

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: W0809 14:02:59.071676   15762 authentication.go:327] No authentication-kubeconfig provided in order to lookup requestheader-client-ca-file in configmap/extensio...ion won't work.

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: W0809 14:02:59.071694   15762 authorization.go:173] No authorization-kubeconfig provided, so SubjectAccessReview of authorization tokens won't work.

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: I0809 14:02:59.071710   15762 controllermanager.go:176] Version: v1.20.2

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: I0809 14:02:59.073931   15762 secure_serving.go:197] Serving securely on [::]:10257

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: I0809 14:02:59.074479   15762 deprecated_insecure_serving.go:53] Serving insecurely on [::]:10252

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: I0809 14:02:59.074521   15762 leaderelection.go:243] attempting to acquire leader lease kube-system/kube-controller-manager...

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: I0809 14:02:59.074829   15762 tlsconfig.go:240] Starting DynamicServingCertificateController

Hint: Some lines were ellipsized, use -l to show in full.



日志如下

[root@node-1 ~]# journalctl -f -u kube-controller-manager

-- Logs begin at Mon 2022-08-08 16:43:56 CST. --

Aug 09 14:02:58 node-1 kube-controller-manager[15762]: I0809 14:02:58.001579   15762 flags.go:59] FLAG: --volume-host-cidr-denylist="[]"

Aug 09 14:02:58 node-1 kube-controller-manager[15762]: I0809 14:02:58.484634   15762 serving.go:331] Generated self-signed cert in-memory

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: W0809 14:02:59.071659   15762 authentication.go:303] No authentication-kubeconfig provided in order to lookup client-ca-file in configmap/extension-apiserver-authentication in kube-system, so client certificate authentication won't work.

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: W0809 14:02:59.071676   15762 authentication.go:327] No authentication-kubeconfig provided in order to lookup requestheader-client-ca-file in configmap/extension-apiserver-authentication in kube-system, so request-header client certificate authentication won't work.

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: W0809 14:02:59.071694   15762 authorization.go:173] No authorization-kubeconfig provided, so SubjectAccessReview of authorization tokens won't work.

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: I0809 14:02:59.071710   15762 controllermanager.go:176] Version: v1.20.2

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: I0809 14:02:59.073931   15762 secure_serving.go:197] Serving securely on [::]:10257

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: I0809 14:02:59.074479   15762 deprecated_insecure_serving.go:53] Serving insecurely on [::]:10252

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: I0809 14:02:59.074521   15762 leaderelection.go:243] attempting to acquire leader lease kube-system/kube-controller-manager...

Aug 09 14:02:59 node-1 kube-controller-manager[15762]: I0809 14:02:59.074829   15762 tlsconfig.go:240] Starting DynamicServingCertificateController


0 回复 有任何疑惑可以回复我~
提问者 慕前端304893 2022-08-09 17:10:47

https://img1.sycdn.imooc.com//szimg/62f2247a09cdb71105760185.jpg
查看pods资源为空

0 回复 有任何疑惑可以回复我~
问题已解决,确定采纳
还有疑问,暂不采纳
微信客服

购课补贴
联系客服咨询优惠详情

帮助反馈 APP下载

慕课网APP
您的移动学习伙伴

公众号

扫描二维码
关注慕课网微信公众号