Kubernetes集群控制之ControllerManager
部署
添加启动脚本
[root@lab-26 ctchat]# vi /opt/kubernetes/server/bin/kube-controller-manager.sh
#!/bin/sh ./kube-controller-manager --cluster-cidr 172.152.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 192.168.0.0/16 --root-ca-file ./cert/ca.pem --v 2
添加supervisor脚本
[root@lab-26 ctchat]# vi /etc/supervisord.d/kube-conntroller-manager.ini
[program:kube-controller-manager-152-106] 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) killasgroup=true stopasgroup=true
启动服务
[root@lab-26 ctchat]# supervisorctl update kube-controller-manager-152-106: added process group [root@lab-26 ctchat]# supervisorctl status etcd-server-152-106 RUNNING pid 22579, uptime 3:49:06 kube-apiserver-152-106 RUNNING pid 21423, uptime 2:44:14 kube-controller-manager-152-106 RUNNING pid 1799, uptime 0:01:04
启动成功之后该服务部署完毕。