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

add config to solve by custom dns server #414

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

Conversation

Smityz
Copy link
Contributor

@Smityz Smityz commented Aug 9, 2023

solve: tikv/client-go#829

I have provided a tool for client-rust that allows for the customization of DNS server addresses. This way, by only exposing the coreDNS address of the k8s cluster, it is possible to achieve client access to tikv across k8s clusters.

Signed-off-by: Smityz <[email protected]>
@andylokandy
Copy link
Collaborator

The DNS/cloud/k8s should be transparent to tikv's client. It could be done by the outer code who is the caller of the client.

@Smityz
Copy link
Contributor Author

Smityz commented Dec 18, 2023

Users can modify system settings to use the correct DNS address, but it requires root permission and not inconvenient.

@andylokandy
Copy link
Collaborator

andylokandy commented Dec 18, 2023

The client user must be another rust code that are using the client. So that there is room for such customization without needing root permission. e.g. Resolve the dns then pass ip to the tikv client

@Smityz
Copy link
Contributor Author

Smityz commented Dec 18, 2023

When TiKV runs on Kubernetes, PD stores the domain of the TiKV node instead of its IP address. Therefore, this function must be configured in the client.

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

Successfully merging this pull request may close these issues.

2 participants