kubespray

82 Tags

152 MiB

Tree: ce776f0f6a

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	6 years ago
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	7 years ago
RongZhang	67ffd8e923	Add etcd-events cluster for kube-apiserver (#2385 ) Add etcd-events cluster for kube-apiserver	7 years ago
Matthew Mosesohn	dc6a17e092	Use include/import tasks (#2192 ) import_tasks will consume far less memory, so it should be used whenever it is compatible.	7 years ago
Steve Mitchell	e45b30d033	Add etcd key and cert environment variables for use with client auth	7 years ago
chenhonggc	c7910b51a1	--peers DEPRECATED - --endpoints should be used instead (#1943 )	7 years ago
Matthew Mosesohn	514359e556	Improve etcd scale up (#1846 ) Now adding unjoined members to existing etcd cluster occurs one at a time so that the cluster does not lose quorum.	7 years ago