Rebuilding first server in HA setup

[gmautner]

Rebuilding first server in HA setup

[dereknola]

This playbook assumes that the first node listed under server hosts is the init node.

So if you swap the first node with another server node, and then use the ansible-playbook --limit flag, you could trick the playbook into initializing the first node again, but this time as a secondary node. You also need to change the api_endpoint to be one of the other two still up servers.

Initial inventory:

k3s_cluster:
  children:
    server:
      hosts:
        192.16.35.10:
        192.16.35.11:
        192.16.35.12:
        
vars:         
  api_endpoint: 192.16.35.10

So you uninstall k3s on 192.16.35.10. Now make your inventory look like:

k3s_cluster:
  children:
    server:
      hosts:
        192.16.35.11:
        192.16.35.10:
        192.16.35.12:
        
vars:         
  api_endpoint: 192.16.35.11

And then run: ansible-playbook --limit 192.16.35.10 ./playbook/site.yml and it should reprovision just 192.16.35.10 as a "joining" server, not the initial one.