WireGuard GitHub Action Verifies Tunnel Health and Auto-Cleans CI Connections
A new open-source GitHub Action, ankurk91/wireguard-action, lets CI runners connect to private networks via WireGuard VPN for the duration of a job, eliminating the need to whitelist GitHub IP ranges or maintain self-hosted runners. Unlike existing solutions, it actively verifies the tunnel handshake after connection, failing the step immediately if the peer is unreachable rather than letting jobs silently time out later. The action also automatically tears down the interface and deletes the config file after each run, regardless of whether the job succeeds, fails, or is cancelled. Built with no external dependencies and a minimal Node.js shim over auditable bash, it requires only an Ubuntu runner and an IPv4-only WireGuard config stored as a repository secret. Optional diagnostics mode and a troubleshooting guide address common CI-specific pitfalls, including the absence of IPv6 on GitHub runners and routing conflicts caused by full-tunnel AllowedIPs settings.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in