Skip to content

Issues/cluster from dns#352

Open
pmlopes wants to merge 3 commits into
masterfrom
issues/cluster-from-dns
Open

Issues/cluster from dns#352
pmlopes wants to merge 3 commits into
masterfrom
issues/cluster-from-dns

Conversation

@pmlopes

@pmlopes pmlopes commented Oct 15, 2022

Copy link
Copy Markdown
Member

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

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

@pmlopes

pmlopes commented Apr 9, 2023

Copy link
Copy Markdown
Member Author

@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.

2 participants