-
Notifications
You must be signed in to change notification settings - Fork 193
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
Investigate mechanisms where Broker can be used for public-ip resolution #2351
Comments
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
Currently, Submariner Gateway pod uses a list of external public resolvers for discovering the public-ip associated with the gateway node. While this is working fine, some of the external resolvers throttle/block a host if it believes that the host is making too many API calls in a short duration. There is also some potential security concern with us using external servers which are not under our control.
It would be worth to explore alternatives to this and see if Broker can be used for public-ip resolution.
The text was updated successfully, but these errors were encountered: