When NodeIp only has InternalIp, is it possible to provide a third way to expose services, such as through LB (VIP: VPort)? #2226
Labels
awaiting-maintainer
Block issues from being stale/obsolete/closed
good first issue
These are great first issues. If you are looking for a place to start, start here!
help wanted
We would love help on these issues. Please come help us!
question
I have a question!
Is your feature request related to a problem? Please describe.
When an Agones is deployed privately and NodeIp only has InternalIp, the existing port exposure method cannot be accessed outside the cluster
Describe the solution you'd like
When an Agones is deployed privately and NodeIp only has InternalIp, is it possible to configure an LB according to yaml to access through LB (VIP: VIP: VPort) -> GameServerPod
Describe alternatives you've considered
When an Agones is deployed privately and the NodeIp only has InternalIp, GameServerAllocation can only get the InternalIp: Port of a GameServer, but it is still inaccessible outside the cluster. Therefore, consider mapping this GameServerPod: LB VIP: VPort to DS Container Port, so that the Client can access through VIP: VPort.
Additional context
clinet->LB->GameServerPod
The text was updated successfully, but these errors were encountered: