【K8S运维知识汇总】第2天9:安装部署主控节点控制器/调度器服务

网友投稿 408 2022-09-07

【K8S运维知识汇总】第2天9:安装部署主控节点控制器/调度器服务

集群规划

主机名 角色 ipHDS7-21.host.com controller-manager 10.4.7.21HDS7-22.host.com controller-manager 10.4.7.22注意:这里部署文档以HDS7-21.host.com主机为例,另外一台运算节点安装部署方法类似

创建启动脚本: – 直接上传

HDS7-21.host.com上

# 创建kube-controller-manager启动脚本[root@hdss7-21 ~]# vi /opt/kubernetes/server/bin/kube-controller-manager.sh#!/bin/sh./kube-controller-manager \ --cluster-cidr 172.7.0.0/16 \ --leader-elect true \ --log-dir /data/logs/kubernetes/kube-controller-manager \ --master \ --service-account-private-key-file ./cert/ca-key.pem \ --service-cluster-ip-range 10.254.0.0/16 \ --root-ca-file ./cert/ca.pem \ --v 2[root@hdss7-21 ~]# mkdir -p /data/logs/kubernetes/kube-controller-manager[root@hdss7-21 ~]# chmod +x /opt/kubernetes/server/bin/kube-controller-manager.sh[root@hdss7-21 ~]# vi /etc/supervisord.d/kube-controller-manager.ini[program:kube-controller-manager-7-21]command=/opt/kubernetes/server/bin/kube-controller-manager.sh ; the program (relative uses PATH, can take args)numprocs=1 ; number of processes copies to start (def 1)directory=/opt/kubernetes/server/bin ; directory to cwd to before exec (def no cwd)autostart=true ; start at supervisord start (default: true)autorestart=true ; retstart at unexpected quit (default: true)startsecs=30 ; number of secs prog must stay running (def. 1)startretries=3 ; max # of serial start failures (default 3)exitcodes=0,2 ; 'expected' exit codes for process (default 0,2)stopsignal=QUIT ; signal used to kill process (default TERM)stopwaitsecs=10 ; max num secs to wait b4 SIGKILL (default 10)user=root ; setuid to this UNIX account to run the programredirect_stderr=true ; redirect proc stderr to stdout (default false)stdout_logfile=/data/logs/kubernetes/kube-controller-manager/controller.stdout.log ; stderr log path, NONE for none; default AUTOstdout_logfile_maxbytes=64MB ; max # logfile bytes b4 rotation (default 50MB)stdout_logfile_backups=4 ; # of stdout logfile backups (default 10)stdout_capture_maxbytes=1MB ; number of bytes in 'capturemode' (default 0)stdout_events_enabled=false ; emit events on stdout writes (default false)[root@hdss7-22 supervisord.d]# supervisorctl updatekube-controller-manager-7-22: added process group[root@hdss7-22 supervisord.d]# supervisorctl statusetcd-server-7-22 RUNNING pid 30474, uptime 17:25:13kube-apiserver-7-22 RUNNING pid 30473, uptime 17:25:13kube-controller-manager-7-22 RUNNING pid 32962, uptime 0:00:31

安装kube-scheduler

# 创建kube-scheduler启动脚本[root@hdss7-21 ~]# vi /opt/kubernetes/server/bin/kube-scheduler.sh#!/bin/sh./kube-scheduler \ --leader-elect \ --log-dir /data/logs/kubernetes/kube-scheduler \ --master \ --v 2

[root@hdss7-21 ~]# vi /etc/supervisord.d/kube-scheduler.ini[program:kube-scheduler-7-21]command=/opt/kubernetes/server/bin/kube-scheduler.sh ; the program (relative uses PATH, can take args)numprocs=1 ; number of processes copies to start (def 1)directory=/opt/kubernetes/server/bin ; directory to cwd to before exec (def no cwd)autostart=true ; start at supervisord start (default: true)autorestart=true ; retstart at unexpected quit (default: true)startsecs=30 ; number of secs prog must stay running (def. 1)startretries=3 ; max # of serial start failures (default 3)exitcodes=0,2 ; 'expected' exit codes for process (default 0,2)stopsignal=QUIT ; signal used to kill process (default TERM)stopwaitsecs=10 ; max num secs to wait b4 SIGKILL (default 10)user=root ; setuid to this UNIX account to run the programredirect_stderr=true ; redirect proc stderr to stdout (default false)stdout_logfile=/data/logs/kubernetes/kube-scheduler/scheduler.stdout.log ; stderr log path, NONE for none; default AUTOstdout_logfile_maxbytes=64MB ; max # logfile bytes b4 rotation (default 50MB)stdout_logfile_backups=4 ; # of stdout logfile backups (default 10)stdout_capture_maxbytes=1MB ; number of bytes in 'capturemode' (default 0)stdout_events_enabled=false ; emit events on stdout writes (default false)[root@hdss7-22 bin]# chmod +x /opt/kubernetes/server/bin/kube-scheduler.sh[root@hdss7-22 bin]# mkdir -p /data/logs/kubernetes/kube-scheduler[root@hdss7-22 ~]# supervisorctl update[root@hdss7-22]# supervisorctl statusetcd-server-7-21 RUNNING pid 27300, uptime 18:45:03kube-apiserver-7-21 RUNNING pid 27301, uptime 18:45:03kube-controller-manager-7-21 RUNNING pid 79809, uptime 1:24:14kube-scheduler-7-21 RUNNING pid 81360, uptime 0:54:28

检测健康状态

[root@hdss7-21 bin]# ln -s /opt/kubernetes/server/bin/kubectl /usr/bin/kubectl[root@hdss7-21 bin]# which kubectl/usr/bin/kubectl[root@hdss7-21 bin]# kubectl get csNAME STATUS MESSAGE ERRORscheduler Healthy ok controller-manager Healthy ok etcd-2 Healthy {"health": "true"} etcd-0 Healthy {"health": "true"} etcd-1 Healthy {"health": "true"}

版权声明:本文内容由网络用户投稿,版权归原作者所有,本站不拥有其著作权,亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容,请联系我们jiasou666@gmail.com 处理,核实后本网站将在24小时内删除侵权内容。

上一篇:【K8S运维知识汇总】第2天8:安装部署主控节点服务——L4反代服务
下一篇:休克文案:端午节文案,就这2招!
相关文章

 发表评论

暂时没有评论,来抢沙发吧~