Hey,
theres no need for an excuse :D
Sorry for not answering that quick. I have to do a lot currently :D
You're quite right. As Software Developer and DevOps guy, I tend to play a lot with technologies in my freetime. Thats the reason, why I currently I use kubernetes for my personal projects.
There is also the financial site:
For example, you can get a dedicated 32 Core machine for 0,557€/h at https://www.hetzner.com/cloud. So my Idea was, that I can use the K8s loud, that I already use and put an Crowdrender-agent there and I can dynamically add a big Node, if I want to render something.
The Problem with Cloud servers with public IPs is, that there are a lot of botnets that try to hack each of them. (have experienced it a lot)
The easiest way to prevent this is, if you make the network of the Node private and add a LoadBalancer in front, that only allows traffic to the public ports (e.g. 9669 - 9694).
But the loadbalancer is rather meant to be used with fewer ports (e.g. only 80 and 433).
Then you have an nginx behind it that acts as reverse-proxy and routes traffic to the designated ports.
This is the part, where it would be handy, if one could distinguish the single tcp packets by either a subdomain, or an added path (worker1.domain.com/port1, or something like that).
And yes, I just want to discuss a bit about what could be done with a some changes.
I like your plugin, the Idea behind it and am hoping you can make it popular. :D