charmarr-lib-vpn
VPN gateway charm library for Kubernetes.
Features
- VPN gateway Juju relation interface
- StatefulSet patching utilities for pod-gateway integration
- NetworkPolicy kill switch implementation
- Reusable beyond Charmarr ecosystem
Installation
pip install charmarr-lib-vpn
Usage
Interfaces
from charmarr_lib.vpn.interfaces import (
VPNGatewayProvider,
VPNGatewayRequirer,
VPNGatewayProviderData,
VPNGatewayRequirerData,
VPNGatewayChangedEvent,
)
Gateway Patching (VPN gateway side - gluetun)
from charmarr_lib.vpn import (
reconcile_gateway,
build_gateway_patch,
is_gateway_patched,
)
from charmarr_lib.krm import K8sResourceManager
manager = K8sResourceManager()
provider_data = VPNGatewayProviderData(
vxlan_id=42,
vxlan_ip_network="172.16.0.0/24",
cluster_cidrs="10.1.0.0/16,10.152.183.0/24",
)
# Idempotent reconciliation
result = reconcile_gateway(
manager=manager,
statefulset_name="gluetun",
namespace="vpn-gateway",
data=provider_data,
pod_cidr="10.1.0.0/16",
)
Client Patching (Download client side - qBittorrent)
from charmarr_lib.vpn import (
reconcile_gateway_client,
build_gateway_client_patch,
build_gateway_client_configmap_data,
is_gateway_client_patched,
)
# Create client-side VPN routing
result = reconcile_gateway_client(
manager=manager,
statefulset_name="qbittorrent",
namespace="download-clients",
data=requirer_data,
configmap_name="qbittorrent-vpn-config",
)
Kill Switch (NetworkPolicy)
from charmarr_lib.vpn import (
KillSwitchConfig,
reconcile_kill_switch,
)
# Create NetworkPolicy that blocks non-VPN egress
config = KillSwitchConfig(
app_name="qbittorrent",
namespace="download-clients",
cluster_cidrs=["10.1.0.0/16", "10.152.183.0/24"],
dns_namespace="kube-system",
)
reconcile_kill_switch(manager, "qbittorrent", "download-clients", config)
# Remove kill switch on relation-broken
reconcile_kill_switch(manager, "qbittorrent", "download-clients", None)
Constants
from charmarr_lib.vpn import (
POD_GATEWAY_IMAGE,
DEFAULT_VXLAN_ID,
DEFAULT_VXLAN_IP_NETWORK,
GATEWAY_INIT_CONTAINER_NAME,
GATEWAY_SIDECAR_CONTAINER_NAME,
CLIENT_INIT_CONTAINER_NAME,
CLIENT_SIDECAR_CONTAINER_NAME,
)
Metadata
Release files for charmarr-lib-vpn 0.6.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| charmarr_lib_vpn-0.6.2.tar.gz | 18.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| charmarr_lib_vpn-0.6.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.1 kB
Release files / charmarr_lib_vpn-0.6.2.tar.gz
| Download URL | charmarr_lib_vpn-0.6.2.tar.gz |
|---|---|
| Size | 18.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f02ea4e45c1dfede12b4820583f2db9adb1147779694a0305b6e802aa631b96f
|
|
BLAKE2b-256 checksum How to use checksums |
c3875269113f0899eecf15b87e8cdd7bf64e26d5c376fbb16e4b220d33e4a2e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.
Transparency logRelease files / charmarr_lib_vpn-0.6.2-py3-none-any.whl
| Download URL | charmarr_lib_vpn-0.6.2-py3-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2fd9a5e9dd10fe5f707d0c6336d9b89ec5dc8273aa195c4c745d2ecb87af5eaf
|
|
BLAKE2b-256 checksum How to use checksums |
60985eb6ebfcf34bb0a8aa5d40a6a0560d62ac8f2e2be8425274cccdd17af526
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.
Transparency log