Pritunl supports running multiple instances for load-balancing and high availability with a feature called 'Replicated Servers'. This is something that had bitten us with our prior solution, so we were still smarting from the pain of not being able to reach important resources.

A highly available architecture ensures the VPN will be resilient to failures of a single node or zone so that secure access to internal resources remains possible for engineers. Architectureĭuring design discussions, high availability for the VPN was a key requirement. It has successfully provided us with a feature-rich and stable network access solution. Several blockers were encountered while implementing the VPN on Kubernetes, but once solved, the VPN has ran smoothly and reliably on Kubernetes. This would provide a standard deployment, self-healing capability, monitoring via our usual toolchains, and other benefits. The majority of services that we operate are deployed in Kubernetes, so to maintain parity with team tooling and operations, we opted to host pritunl in one of our Kubernetes clusters.

We chose to implement pritunl, an open source VPN product that supports 3 protocols (OpenVPN, IPSsec, and WireGuard). The Platform Engineering group was asked to provide secure and reliable access to these resources, to replace the outsourced solution that had bridged the gap since December of 2020 when MyFitnessPal was divested from Under Armour. MyFitnessPal engineering runs the large majority of our cloud infrastructure and applications in private VPCs, and interacting with these resources is an important part of an engineer's daily responsibilities. Originally published on the MyFitnessPal Blog Background

Pritunl vpn