kubespray

Commit Graph

Author	SHA1	Message	Date
woopstar	86e3506ae6	Etcd cluster setup makeover The current way to setup the etc cluster is messy and buggy. - It checks for cluster is healthy before the cluster is even created. - The unit files are started on handlers, not in the task, so you mess with "flush handlers". - The join_member.yml is not used. - etcd events cluster is not configured for kubeadm - remove duplicate runs between running the role on etcd nodes and k8s nodes	2018-04-01 21:38:33 +02:00
Andreas Krüger	b9b028a735	Update etcd deployment to use correct cert and key (#2572 ) * Update etcd deployment to use correct cert and key * Update to use admin cert for etcdctl commands * Update handler to use admin cert too	2018-03-31 14:06:09 -04:00
RongZhang	67ffd8e923	Add etcd-events cluster for kube-apiserver (#2385 ) Add etcd-events cluster for kube-apiserver	2018-03-01 11:39:14 +03:00

Author

SHA1

Message

Date

woopstar

86e3506ae6

Etcd cluster setup makeover

The current way to setup the etc cluster is messy and buggy.

- It checks for cluster is healthy before the cluster is even created.
- The unit files are started on handlers, not in the task, so you mess with "flush handlers".
- The join_member.yml is not used.
- etcd events cluster is not configured for kubeadm
- remove duplicate runs between running the role on etcd nodes and k8s nodes

2018-04-01 21:38:33 +02:00

Andreas Krüger

b9b028a735

Update etcd deployment to use correct cert and key (#2572 )

* Update etcd deployment to use correct cert and key

* Update to use admin cert for etcdctl commands

* Update handler to use admin cert too

2018-03-31 14:06:09 -04:00

RongZhang

67ffd8e923

Add etcd-events cluster for kube-apiserver (#2385 )

Add etcd-events cluster for kube-apiserver

2018-03-01 11:39:14 +03:00

3 Commits (70b28288a3037e39c2c7088b515129fb849d61da)