Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When NodeIp only has InternalIp, is it possible to provide a third way to expose services, such as through LB (VIP: VPort)? #2226

Closed
youngwang3 opened this issue Aug 18, 2021 · 6 comments · Fixed by #3129
Assignees
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!

Comments

@youngwang3
Copy link

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

@youngwang3 youngwang3 added the kind/feature New features for Agones label Aug 18, 2021
@markmandel
Copy link
Member

If I'm understanding this correctly, I'm not sure it's possible. This sounds like something that should be managed outside of Agones.

Some thoughts/questions:

We can't be creating a load balancer for every game server, and the extra latency doesn't make sense there either.

Not sure what a "VIP" or "VPort" here is - can you explain that?

I'm not sure I'm reading any kind of solution here. If a node is private, it can't be exposed - so that's on you to determine how it should be exposed. I'm not sure what we should actually do here?

What is this mapping? How would it work? It sounds like it's something you need specific to your use case? It doesn't sound like something generic -- which makes me (at least initially) think that this doesn't belong in the Agones project -- but please expand more, I'd like to completely understand the use case before drawing a conclusion.

@roberthbailey roberthbailey added question I have a question! stale Pending closure unless there is a strong objection. and removed kind/feature New features for Agones labels Dec 21, 2022
@roberthbailey
Copy link
Member

This issue hasn't been updated in a while so I'm going to mark it as stale.

@roberthbailey
Copy link
Member

I will also note that in the time since this question was asked, Quilkin has added support to be a udp proxy for Agones game servers, which may help solve this sort of problem.

@github-actions
Copy link

This issue is marked as obsolete due to inactivity for last 60 days. To avoid issue getting closed in next 30 days, please add a comment or add 'awaiting-maintainer' label. Thank you for your contributions

@markmandel
Copy link
Member

We have #2001 for writing some more docs on websockets, so to close this out, why don't we add a link to Quilkin and it's examples/docs to https://agones.dev/site/docs/third-party-content/examples/ and we can close his issue.

@markmandel markmandel added awaiting-maintainer Block issues from being stale/obsolete/closed help wanted We would love help on these issues. Please come help us! good first issue These are great first issues. If you are looking for a place to start, start here! and removed stale Pending closure unless there is a strong objection. obsolete labels Apr 27, 2023
@Kalaiselvi84
Copy link
Contributor

Please review this PR and let me know if there's anything I can improve - #3129

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants