Remote Nodes for self hosted installs

[endigma]

Summary

The cloud offering of Pangolin has the Remote Nodes. I would like for this feature to be also available for self-hosted installs.

Motivation

It would be nice to be able to self-host the main Pangolin stack at home but route some or all ingress traffic through a cloud VPS or a HA deployment on K8s or etc. This is good both for reliability as well as choosing whether or not a given resource/domain should be pointed at my home IP address or a VPS to proxy it.

It can be useful to be direct for some things, e.g. media, games, streaming, but other cases like a Git server or a website are best served from cloud IP(s) so your home connection is protected.

Proposed Solution

• Make Remote nodes available in self-hosted Pangolin, glued to a particular domain or subdomain.
• Add setting to domain (or possibly resource?) to set which Remote Node is used

Alternatives Considered

• Running a second Pangolin instance or another proxy, not favorable because it complicates management and requires a full stack in the cloud, harder to scale

Additional Context

The feature of glueing a domain to a particular remote node would also be useful in Pangolin Cloud, especially in cases like putting the remote Node's IP in a VPN or private network is kinda like a pseudo-client-thing for a whole network segment.

[endigma]

The remote node being available as a container would also be great so it could be deployed easily to services like Koyeb, managed Kubernetes, etc