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
30 lines
969 B
YAML
30 lines
969 B
YAML
---
|
|
- name: Install | Copy etcdctl binary from docker container
|
|
command: sh -c "{{ docker_bin_dir }}/docker rm -f etcdctl-binarycopy;
|
|
{{ docker_bin_dir }}/docker create --name etcdctl-binarycopy {{ etcd_image_repo }}:{{ etcd_image_tag }} &&
|
|
{{ docker_bin_dir }}/docker cp etcdctl-binarycopy:/usr/local/bin/etcdctl {{ bin_dir }}/etcdctl &&
|
|
{{ docker_bin_dir }}/docker rm -f etcdctl-binarycopy"
|
|
register: etcd_task_result
|
|
until: etcd_task_result.rc == 0
|
|
retries: 4
|
|
delay: "{{ retry_stagger | random + 3 }}"
|
|
changed_when: false
|
|
when: etcd_cluster_setup
|
|
|
|
- name: Install etcd launch script
|
|
template:
|
|
src: etcd.j2
|
|
dest: "{{ bin_dir }}/etcd"
|
|
owner: 'root'
|
|
mode: 0750
|
|
backup: yes
|
|
when: etcd_cluster_setup
|
|
|
|
- name: Install etcd-events launch script
|
|
template:
|
|
src: etcd-events.j2
|
|
dest: "{{ bin_dir }}/etcd-events"
|
|
owner: 'root'
|
|
mode: 0750
|
|
backup: yes
|
|
when: etcd_events_cluster_setup
|