VPN networking
Configure a VPN provider for supported apps.
For charts that support VPN routing, configure a provider and assign it to an app in VPN settings. The supported setup can use WireGuard or OpenVPN credentials and adds a Gluetun sidecar to the app’s pod when enabled. VPN routing requires a working provider and /dev/net/tun on the node. The firewall kill switch is enabled by default and can be overridden per app; explicitly allowed outbound subnets may bypass the tunnel. VPN is off until configured.
How it works
When enabled for a supported app, the chart runs Gluetun beside the app in the same pod. The sidecar establishes the configured tunnel and provides the pod’s VPN egress path; the firewall kill switch is intended to prevent ordinary outbound traffic if the tunnel is unavailable. Confirm the provider, node TUN support, allowed subnet exceptions and resulting connectivity for your own setup.
These views show or configure aspects of your Kubernetes cluster. Availability and behavior depend on your deployed components, cluster configuration and supported app charts.
Check the result: Use Kubernetes workload status and the relevant chart documentation to verify behavior. Observability views show reported state and do not themselves enforce network or storage boundaries.