Hello! I'm currently using Netmaker primarily as a way to handle remote access to a VPC ("corporate VPN"). I.e. running a node that acts as both an ingress and egress gateway and using Netmaker to manage the external clients (and manage who can manage the external clients). It's been splendid for our current setup, which is relatively simple. However, moving forward the idea is to both utilize Netmaker for more as well as try to set up a HA remote access. I'm just gonna go ahead and describe how I imagine this kind of management would look/work without regards to the actual complexity of implementation. So this is kind of a preface of "I realize this might be ridiculous" but it could be a good jumping-off point. So my idea would entail some key steps 1. Ingress gateway would be its own concept and consist of an

endpoint

, a collection of

external clients

and a collection of

nodes

and an optional

egress

2. An external client would be tied to both an ingress gateway and a user. A user would be able to have several external clients within an ingress. The workflow here (for me) would be that I (as an admin) would create an ingress gateway and set the endpoint to a loadbalancer I have configured ahead of time. I would then register a collection of nodes to this ingress and Netmaker would ensure that they have exactly equal configurations (so that they essentially "act as the same node" but with different private IPs). I would then grant access to the users I administer so that each user can log in (preferably with OAuth) and create and manage their own external clients within this Network & Ingress. So e.g if one of my users wants one configuration for the office and one for the home computer they can do that, and I can still both see and manage those (and revoke them). Obviously, they wouldn't be able to see each other's configuration and secrets.