add config to solve by custom dns server #414
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Smityz <[email protected]>
Signed-off-by: Smityz <[email protected]>
|
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. |
|
Users can modify system settings to use the correct DNS address, but it requires root permission and not inconvenient. |
|
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 |
|
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.