Skip to content

Latest commit

 

History

History
28 lines (23 loc) · 986 Bytes

File metadata and controls

28 lines (23 loc) · 986 Bytes

Requirements

External

  1. Consul
    1. Must be installed/configured on the target hosts/inventory.
    2. (see example_environment.yml).
      • The generated master token can be used in a pinch, and can be acquierd directly from a consul server host, by running:
        cat /var/lib/consul/config.json | grep master
    3. Consul DNS: must be configured and working properly
  2. Vault
    1. Vault must be installed and bootstrapped on all primary datacenter server nodes.
    2. A Vault token with access to the kv-v1 target namespace must be generated.

Internal

Playbook Variables

  1. consul_master_key: Consul ACL token used to generate node agent tokens, etc.
  2. vault_master_token: Vault token with access to the kv-v1 store, used to store Consul ACLs.
  3. target_vault_primary_datacenter: The Consul datacenter where Vault has been installed, initialized, and unsealed (on all nodes).