setsid etcd -name etcd -data-dir /var/lib/etcd -listen-client-urls http://0.0.0.0:2379,http://0.0.0.0:4001 -advertise-client-urls http://0.0.0.0:2379,http://0.0.0.0:4001 > etcd.log
etcdctl -C http://localhost:4001 set /coreos.com/network/config '{"Network":"10.0.0.0/16"}' 不能有代理
etcdctl -C http://localhost:4001 set /atomic.io/network/config '{"Network":"10.0.0.0/16"}'
[root@mhc dbcm-opsapi]# etcdctl -C http://localhost:4001 get /coreos.com/network/config
{"Network":"10.0.0.0/16"}
setsid flanneld -etcd-endpoints=http://109.105.4.65:4001 > flanneld.log
setsid kube-apiserver --logtostderr=true --v=0 --etcd-servers=http://109.105.4.65:4001 --insecure-bind-address=0.0.0.0 --insecure-port=8080 --service-cluster-ip-range=10.254.0.0/16 > apiserver.log 2>&1
setsid kube-controller-manager --logtostderr=true --v=0 --master=http://109.105.4.65:8080 > controller-manager.log 2>&1
setsid kube-scheduler --logtostderr=true --v=0 --master=http://109.105.4.65:8080 > scheduler.log 2>&1
setsid kube-proxy --logtostderr=true --v=0 --master=http://109.105.4.65:8080 > proxy.log 2>&1
setsid kubelet --logtostderr=true --v=0 --address=0.0.0.0 --cgroup-driver=systemd --api-servers=http://109.105.4.65:8080 > kubelet.log 2>&1
[root@mhc k8s]# kubectl get componentstatus ()
NAME STATUS MESSAGE ERROR
controller-manager Healthy ok
scheduler Healthy ok
etcd-0 Healthy {"health": "true"}