86e3506ae6
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 |
||
|---|---|---|
| .. | ||
| adduser | ||
| bastion-ssh-config | ||
| bootstrap-os | ||
| dnsmasq | ||
| docker | ||
| download | ||
| etcd | ||
| kubernetes | ||
| kubernetes-apps | ||
| kubespray-defaults | ||
| network_plugin | ||
| remove-node | ||
| reset | ||
| rkt | ||
| upgrade | ||
| vault | ||