mirror of
https://gitlab.archlinux.org/archlinux/infrastructure.git
synced 2026-09-06 23:34:10 +02:00
Also rearranged the documentation a bit.
Fixes: 27553ab3 ("Remove the WG private keys from the vault and store them only on the servers")
1.0 KiB
1.0 KiB
WireGuard
Many of our servers communicate through wireguard VPN with each others. If you need to collect logs with loki and metrics with prometheus for dashboards you need to have a wiregauard IP.
Setting up
-
For a new server add a new unused wireguard IP and set the following in
host_vars/<fqdn>/miscwireguard_address: <wg-ip> wireguard_public_key: <wg-pubkey> -
Generate the private key on the server with
wg genkey | systemd-creds encrypt - /etc/credstore.encrypted/network.wireguard.private.wg0and restart systemd-networkd withsystemctl restart systemd-networkd -
Get public key with:
systemd-creds decrypt /etc/credstore.encrypted/network.wireguard.private.wg0 - | wg pubkey -
Execute
wireguardandprometheusroles onmonitoring.archlinux.org.ymlplaybook to get data from the server
Tips:
- Pick next available IP for Wireguard from
grep -r wireguard_address host_vars/ | cut -f3 -d: | sort -h - Wireguard key generation docs: https://www.wireguard.com/quickstart/#key-generation