blob: 11920f24c63a8ec7596ecbf59e3239f6e4e42d03 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
#cloud-config
# vim: syntax=yaml
#
# This is the configuration syntax that the wireguard module
# will know how to understand.
#
#
wireguard:
# All wireguard interfaces that should be created. Every interface will be named
# after `name` parameter and config will be written to a file under `config_path`.
# `content` parameter should be set with a valid Wireguard configuration.
interfaces:
- name: wg0
config_path: /etc/wireguard/wg0.conf
content: |
[Interface]
PrivateKey = <private_key>
Address = <address>
[Peer]
PublicKey = <public_key>
Endpoint = <endpoint_ip>:<endpoint_ip_port>
AllowedIPs = <allowedip1>, <allowedip2>, ...
# The idea behind readiness probes is to ensure Wireguard connectivity before continuing
# the cloud-init process. This could be useful if you need access to specific services like
# an internal APT Repository Server (e.g Landscape) to install/update packages.
readinessprobe:
- 'systemctl restart service'
- 'curl https://webhook.endpoint/example'
- 'nc -zv apt-server-fqdn 443'
|
