Expose Game Servers via a cloud Load Balancer

[dgkanatsios]

In cloud environments, it might be unrealistic to have a Public IP per Node. For these scenarios, we should examine using a vendor-specific Load Balancer with a Public IP that would act as a reverse proxy-gateway for the game server ports. Rough design includes an additional controller created as a separate deployment that would:

• set up a Kubernetes watch to all GameServer CR instances
• every time there is a new one, it would create a mapping to the LB
• every time one is deleted, it would delete the mapping

On Azure specifically, we'd need to have this controller having an Azure identity (either with a service principal or preferably with a managed identity) and do ARM operations to the LB.

[dgkanatsios]

One other option which could also be more "cloud portable" is to use an Ingress resource. That would help in scenarios where we need SSL termination, like WebGL servers.

[dgkanatsios]

Closing as we created a simple approach with Traefik/Kubernetes Ingress here: https://github.com/dgkanatsios/thundernetescontrib/tree/main/traefikingress

Works great for HTTP/HTTPS (like WebGL) game servers.