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

Issues/cluster from dns #352

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Issues/cluster from dns #352

wants to merge 3 commits into from

Conversation

pmlopes
Copy link
Member

@pmlopes pmlopes commented Oct 15, 2022

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 memoryDB for example.

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
Copy link

Could this be helpful when using ElastiCache cluster with configuration endpoint?

@pmlopes
Copy link
Member Author

pmlopes commented Apr 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants