Server IP : 51.89.169.208 / Your IP : 18.118.171.154 Web Server : Apache System : Linux ns3209505.ip-198-244-202.eu 4.18.0-553.27.1.el8_10.x86_64 #1 SMP Tue Nov 5 04:50:16 EST 2024 x86_64 User : yellowleaf ( 1019) PHP Version : 7.4.33 Disable Function : exec,passthru,shell_exec,system MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /proc/self/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'