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

Make a better job at documenting that STUNner ignores the port in backend Services #87

Closed
rg0now opened this issue May 10, 2023 · 1 comment
Assignees
Labels

Comments

@rg0now
Copy link
Member

rg0now commented May 10, 2023

It seems that we have to live with this monstrosity until support for service-port ranges lands in Kubernetes. The only way we can deal with the fact that media servers use entire port ranges is to ignore the Service port in UDPRoutes. This, however, often confuses users (quite understandably).

For now, we have to make a better job at documenting the fact that we completely omit ports in UDPRoute backend Services.

@rg0now rg0now self-assigned this May 10, 2023
@rg0now
Copy link
Member Author

rg0now commented Feb 1, 2024

This has been addressed in 27026ab.

@rg0now rg0now closed this as completed Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant