pingcap / pingcap/tidb-operator
Allow PD/TiKV port configuration
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? Please describe:
We try to setup TiDB in the environment, which has a strict range of ports allowed to use.
Describe the feature you'd like:
Allow tidb CR to specify which ports to use for TiKV and PD. Right now port numbers are hardcoded: https://github.com/pingcap/tidb-operator/blob/master/charts/tidb-cluster/templates/scripts/_start_pd.sh.tpl#L64-L66
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
Start with charts/tidb-cluster/templates/scripts/_start_pd.sh.tpl at lines 64–66 and trace how TiDB CR settings reach the chart templates. Identify the corresponding PD and TiKV port configuration points, then verify that rendered resources use CR-specified ports rather than hardcoded values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100