You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
activity occurs. 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
activity occurs. Thank you for your contributions.
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: