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
15 lines
390 B
YAML
15 lines
390 B
YAML
---
|
|
- name: Refresh config | Create etcd config file
|
|
template:
|
|
src: etcd.env.j2
|
|
dest: /etc/etcd.env
|
|
notify: restart etcd
|
|
when: is_etcd_master and etcd_cluster_setup
|
|
|
|
- name: Refresh config | Create etcd-events config file
|
|
template:
|
|
src: etcd-events.env.j2
|
|
dest: /etc/etcd-events.env
|
|
notify: restart etcd-events
|
|
when: is_etcd_master and etcd_events_cluster_setup
|