Server IP : 209.38.156.173 / Your IP : 216.73.216.122 [ Web Server : Apache/2.4.52 (Ubuntu) System : Linux lakekumayuhotel 5.15.0-136-generic #147-Ubuntu SMP Sat Mar 15 15:53:30 UTC 2025 x86_64 User : root ( 0) PHP Version : 8.1.2-1ubuntu2.22 Disable Function : NONE Domains : 2 Domains MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /proc/1534260/root/usr/share/doc/cloud-init/examples/ |
Upload File : |
#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'