6部署 controller-manager scheduler
阿新 • • 發佈：2020-07-17
安裝部署主控節點控制器/排程器服務 叢集規劃 主機名 角色 ip HDS7-121.host.com controller-manager 192.168.1.121 HDS7-122.host.com controller-manager 192.168.1.122 注意：這裡部署文件以HDS7-121.host.com主機為例，另外一臺運算節點安裝部署方法類似 建立啟動指令碼： -- 直接上傳 HDS7-121.host.com上 [root@hdss7-121 ~]# 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 http://127.0.0.1:8080 \ --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-121 ~]# mkdir -p /data/logs/kubernetes/kube-controller-manager [root@hdss7-121 ~]# chmod +x /opt/kubernetes/server/bin/kube-controller-manager.sh [root@hdss7-121 ~]# vi /etc/supervisord.d/kube-conntroller-manager.ini [program:kube-controller-manager-7-121] 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 program redirect_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 AUTO stdout_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-122 supervisord.d]# supervisorctl update kube-controller-manager-7-22: added process group [root@hdss7-122 supervisord.d]# supervisorctl status etcd-server-7-122 RUNNING pid 30474, uptime 17:25:13 kube-apiserver-7-122 RUNNING pid 30473, uptime 17:25:13 kube-controller-manager-7-122 RUNNING pid 32962, uptime 0:00:31 安裝kube-scheduler [root@hdss7-121 ~]# vi /opt/kubernetes/server/bin/kube-scheduler.sh #!/bin/sh ./kube-scheduler \ --leader-elect \ --log-dir /data/logs/kubernetes/kube-scheduler \ --master http://127.0.0.1:8080 \ --v 2 [root@hdss7-21 ~]# vi /etc/supervisord.d/kube-scheduler.ini [program:kube-scheduler-7-121] 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 program redirect_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 AUTO stdout_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-122 bin]# chmod +x /opt/kubernetes/server/bin/kube-scheduler.sh [root@hdss7-122 bin]# mkdir -p /data/logs/kubernetes/kube-scheduler [root@hdss7-22 ~]# supervisorctl update [root@hdss7-21 bin]# supervisorctl status etcd-server-7-21 RUNNING pid 27300, uptime 18:45:03 kube-apiserver-7-21 RUNNING pid 27301, uptime 18:45:03 kube-controller-manager-7-21 RUNNING pid 79809, uptime 1:24:14 kube-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 cs NAME STATUS MESSAGE ERROR scheduler Healthy ok controller-manager Healthy ok etcd-2 Healthy {"health": "true"} etcd-0 Healthy {"health": "true"} etcd-1 Healthy {"health": "true"}