pingcap / pingcap/tidb-operator
Allow configure TiKV to use IP addresses instead of DNS
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Is your feature request related to a problem?
We try to use tidb-operator to deploy TiKV cluster w/o TiDB layer, so TiKV client is usually deployed to other k8s cluster and don't have access top internal kube-dns with information about TiKV cluster. Also DNS could be cached at some layers and result in the issues when TiKV/PD node is replaced.
Describe the feature you'd like:
We would like to have an ability to configure TiKV to use IP address rather than ${POD_NAME}.${PEER_SERVICE_NAME}.${NAMESPACE}.svc DNS names.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files or tests; begin at the TiKV/PD address-generation and Kubernetes configuration entry points. Define how IP-based endpoints are configured instead of the shown DNS names, then verify the resulting cluster and client configuration supports node replacement without relying on internal kube-DNS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100