Install and deploy the master node controller/scheduler service
Cluster planning
主机名 角色 ip
hdss-1-21.host.com controller-manager 192.168.1.21
hdss-1-22.host.com controller-manager 192.168.1.22Note: The deployment document here takes the hdss-1-22.host.com host as an example, and the installation and deployment methods for another computing node are similar.
Edit kube-controller-manager.sh to execute the script
[root@hdss-1-22 bin]# ls
apiextensions-apiserver conf kube-apiserver kubectl kube-scheduler
cert hyperkube kube-apiserver.sh kubelet mounter
cloud-controller-manager kubeadm kube-controller-manager kube-proxy
[root@hdss-1-22 bin]# vim 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 2Create a directory in the script
[root@hdss-1-22 bin]# mkdir -p /data/logs/kubernetes/kube-controller-manager
[root@hdss-1-22 bin]# chmod +x /opt/kubernetes/server/bin/kube-controller-manager.shEdit the configuration file kube-conntroller-manager.ini for supervisord background startup
[root@hdss-1-22 bin]# vi /etc/supervisord.d/kube-conntroller-manager.ini
[program:kube-controller-manager-1-22]
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 Start and view process information
[root@hdss-1-22 bin]# supervisorctl update
kube-controller-manager-1-22: added process group
[root@hdss-1-22 bin]# supervisorctl status
etcd-server-1-22 RUNNING pid 7483, uptime 3:41:15
kube-apiserver-1-22 RUNNING pid 6941, uptime 3:41:24
kube-controller-manager-1-22 RUNNING pid 10794, uptime 0:00:48Install kube-scheduler, edit the execution script
[root@hdss-1-22 bin]# 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 2Edit supervisord background startup configuration file kube-scheduler.ini
[root@hdss-1-22 bin]# vi /etc/supervisord.d/kube-scheduler.ini
[program:kube-scheduler-1-22]
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)Create a directory and grant execution permissions
[root@hdss-1-22 bin]# chmod +x /opt/kubernetes/server/bin/kube-scheduler.sh
[root@hdss-1-22 bin]# mkdir -p /data/logs/kubernetes/kube-scheduler
[root@hdss-1-22 bin]# Start and view status
[root@hdss-1-22 bin]# supervisorctl update
kube-scheduler-1-22: added process group
[root@hdss-1-22 bin]# supervisorctl status
etcd-server-1-22 RUNNING pid 7483, uptime 3:46:54
kube-apiserver-1-22 RUNNING pid 6941, uptime 3:47:03
kube-controller-manager-1-22 RUNNING pid 10794, uptime 0:06:27
kube-scheduler-1-22 RUNNING pid 10864, uptime 0:00:49Establish a soft link to view the status of the cluster
[root@hdss-1-22 bin]# ln -s /opt/kubernetes/server/bin/kubectl /usr/bin/kubectl
[root@hdss-1-22 bin]# which kubectl
/usr/bin/kubectl
[root@hdss-1-22 bin]# kubectl get cs
NAME STATUS MESSAGE ERROR
scheduler Healthy ok
controller-manager Healthy ok
etcd-1 Healthy {"health": "true"}
etcd-2 Healthy {"health": "true"}
etcd-0 Healthy {"health": "true"}
[root@hdss-1-22 bin]#
