Put your own username/password converted in base64 formatĮcho "my_login_username_2VPNprovider" | base64 -> bXlfbG9naW5fdXNlcm5hbWVfMlZQTnByb3ZpZGV圜g=Įcho "my_login_password_2VPNprovider" | base64 -> bXlfbG9naW5fcGFzc3dvcmRfMlZQTnByb3ZpZGV圜g= The authentication to the VPN provider is configured in secrets.yaml on base64 translation. If you want to rename it, remember to change the label in all the following yaml Inside it all the K8s components will be installed (services, pod, pv, pvc, secret). The namespace.yaml creates the "vpn" namespace. Change the internal dns server according to your k8s setup "Add-route" busybox: controller container to add the route to K8s internal dns server since the default gateway is being deleted in the shared pod namespace by openvpn-client. It creates an emule container listening on 4080 It creates a SOCKS5 proxy server listening on 1080 (customizable)Įmule: based on the project of angeletor/mldonkey. Socks5 server: based on the project of xkuma/socks5.
Take a look to the original project to change the parameters according to your VPN provider The deployment creates a vpn connection to the VyprVPN provider at UK location. Openvpn-client: based on the project of chuckremes/openvpn-client. There are 4 containers inside the created POD: openvpn-client, socks5 server, emule client, busybox container to add the route to the internal DNS K8s server (coreDNS) It permits the use of a vpn connection to shadow all torrent/emule activities by a SOCKS5 server (as a proxy for your torrent client) or directly inside the emule container thanks to the webgui admin page.
0 kommentar(er)
