Ah, you “work” in “marketing”?
It doesn’t. It carries you by having a module for absolutely everything even shooting yourself in the foot.
No, No, they don’t understand everything and nothing!
I run a 2 node k3s cluster. There are a few small advantages over docker swarm, built-in network policies to lock down my VPN/Torrent pod being the main one.
Other than that writing kubernetes yaml files is a lot more verbose than docker-compose. Helm does make it bearable, though.
Due to real-life my migration to the cluster is real slow, but the goal is to move all my services over.
It’s not “better” than compose but I like it and it’s nice to have worked with it.
You dynamically request “a port” from the vpn gateway and it returns your port number.
As long as your nat-pmp-client keeps refreshing the port, it should stay the same. The timeout is rather low (60s afaik) so it probably wouldn’t survive restarts.
There’s a docker image that automates this for qbittorrent, but it shouldn’t be overly complicated to adapt the script to other clients, if they can be configured via an API.
Mullvad stopped providing port forwards, so they’re not ideal for torrenting anymore. They were great before.
Thanks for the pointers that sounds quite doable. I’ll give it a shot to mash it into my helm chart. Will report back.
Edit:
Got ProtonVPN and qbittorrent working with manual port-forwarding. The natmap-docker image wants to use the docker socket which is not available in my kubernetes cluster.
I’m currently reworking the script to run without docker access.
Mind sharing some details of your trickery? I’m in the same situation currently
They should not be worried, they should be educated.
If you worry a new user enough they’ll go back to Windows or Apple because there’s less scary warnings there.
We need to make the transition as pain free as possible. Learning about the joys of kernel compilation and SELinux can come later.
The first step is "Hey, this is as usable as Windows, without stupid ads in the start menu.