kubespray

81 Tags

150 MiB

Tree: 4a1be18361

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
Spencer Smith	0126168472	provide environment for rkt trust and run with etcd	7 years ago
Matthew Mosesohn	a56738324a	Move set_facts to kubespray-defaults defaults These facts can be generated in defaults with a performance boost. Also cleaned up duplicate etcd var names.	7 years ago
Brad Beam	8dc19374cc	Allowing etcd to run via rkt	8 years ago