Server : Apache/2.4.41 (Ubuntu) System : Linux journalup 5.4.0-198-generic #218-Ubuntu SMP Fri Sep 27 20:18:53 UTC 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.33 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, Directory : /usr/share/doc/cloud-init/examples/ |
#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'