- Notifications
You must be signed in to change notification settings - Fork120
Issues/cluster from dns#352
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Signed-off-by: Paulo Lopes <pmlopes@gmail.com>
Signed-off-by: Paulo Lopes <pmlopes@gmail.com>
Signed-off-by: Paulo Lopes <pmlopes@gmail.com>
OmerShemesh commentedApr 9, 2023
Could this be helpful when using ElastiCache cluster with configuration endpoint? |
pmlopes commentedApr 9, 2023
@OmerShemesh yes, AWS exposes the full cluster nodes in the DNS record of the service, recently they also have support for custom authentication using IAM. This PR is a start prototype to collect the cluster endpoints from the DNS but isn't finished. It should also be guarded by a flag to avoid extra startup delays. |
Motivation:
Cluster deployments that use the DNS to announce the initial set of servers composing the cluster can now be discovered by the cluster client instead of requiring users to specify the initial list of servers.
This is the case of AWS
memoryDBfor example.