[k8s]api controller schedular service的启动脚本参数
2017-05-10 18:25
316 查看
[root@node131 bin]# cat kube-apiserver.service [Unit] Description=Kubernetes API Server Documentation=https://github.com/GoogleCloudPlatform/kubernetes After=network.target [Service] ExecStart=/root/local/bin/kube-apiserver \ --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,ResourceQuota \ --advertise-address=192.168.6.131 \ --bind-address=192.168.6.131 \ --insecure-bind-address=192.168.6.131 \ --authorization-mode=RBAC \ --runtime-config=rbac.authorization.k8s.io/v1alpha1 \ --kubelet-https=true \ --experimental-bootstrap-token-auth \ --token-auth-file=/etc/kubernetes/token.csv \ --service-cluster-ip-range=10.254.0.0/16 \ --service-node-port-range=8400-9000 \ --tls-cert-file=/etc/kubernetes/ssl/kubernetes.pem \ --tls-private-key-file=/etc/kubernetes/ssl/kubernetes-key.pem \ --client-ca-file=/etc/kubernetes/ssl/ca.pem \ --service-account-key-file=/etc/kubernetes/ssl/ca-key.pem \ --etcd-cafile=/etc/kubernetes/ssl/ca.pem \ --etcd-certfile=/etc/kubernetes/ssl/kubernetes.pem \ --etcd-keyfile=/etc/kubernetes/ssl/kubernetes-key.pem \ --etcd-servers=https://192.168.6.131:2379,https://192.168.6.132:2379,https://192.168.6.133:2379 \ --enable-swagger-ui=true \ --allow-privileged=true \ --apiserver-count=3 \ --audit-log-maxage=30 \ --audit-log-maxbackup=3 \ --audit-log-maxsize=100 \ --audit-log-path=/var/lib/audit.log \ --event-ttl=1h \ --v=2 Restart=on-failure RestartSec=5 Type=notify LimitNOFILE=65536 [Install] WantedBy=multi-user.target
[root@node131 bin]# cat kube-controller-manager.service [Unit] Description=Kubernetes Controller Manager Documentation=https://github.com/GoogleCloudPlatform/kubernetes [Service] ExecStart=/root/local/bin/kube-controller-manager \ --address=127.0.0.1 \ --master=http://192.168.6.131:8080 \ --allocate-node-cidrs=true \ --service-cluster-ip-range=10.254.0.0/16 \ --cluster-cidr=172.30.0.0/16 \ --cluster-name=kubernetes \ --cluster-signing-cert-file=/etc/kubernetes/ssl/ca.pem \ --cluster-signing-key-file=/etc/kubernetes/ssl/ca-key.pem \ --service-account-private-key-file=/etc/kubernetes/ssl/ca-key.pem \ --root-ca-file=/etc/kubernetes/ssl/ca.pem \ --leader-elect=true \ --v=2 Restart=on-failure RestartSec=5 [Install] WantedBy=multi-user.target
[root@node131 bin]# cat kube-scheduler.service [Unit] Description=Kubernetes Scheduler Documentation=https://github.com/GoogleCloudPlatform/kubernetes [Service] ExecStart=/root/local/bin/kube-scheduler \ --address=127.0.0.1 \ --master=http://192.168.6.131:8080 \ --leader-elect=true \ --v=2 Restart=on-failure RestartSec=5 [Install] WantedBy=multi-user.target
相关文章推荐
- [k8s]k8s api-server启动systemd参数分析
- AIDL中遇到的问题,记录一下 + 避免绑定启动service 后 activity 与service 之间参数为null的情况
- Service启动及参数
- 从Service中启动Acitivity时向Activity中传递参数
- Dubbo 官方 shell 启动脚本(带JVM参数)
- Windows Service 使用参数安装DEMO,可使用控制台启动方式进行调试,服务安装完后立即启动
- 手动添加service服务启动脚本
- 探索 OpenStack 之(11):cinder-api Service 启动过程分析 以及 WSGI / Paste deploy / Router 等介绍
- (OK) Fedora 24 开机自动启动脚本 - rc.local - rc-local.service
- Android init.rc如何启动service去执行sh脚本
- 如何在命令行脚本中启动带参数的Windows服务
- linux启动脚本和service、chkconfig
- k8s 启动service样例,端口访问分析
- Eclipse 配置Tomcat启动参数 Java EE IDE for Web Developers. Version: Helios Service Release 2
- Android init.rc如何启动service去执行sh脚本
- linux启动脚本和service、chkconfig
- 友善之臂开发板启动脚本配置以及fa-network-service后台服务对网络的配置
- php-fpm服务启动脚本 service chkconfig
- linux启动脚本和service、chkconfig
- linux tomcat service 方式启动脚本