pingcap / pingcap/tidb-operator
Always use FQDN in config
Open
Nobody has claimed this yet.
v2
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Now we use {svc}.{namespace} and {pod}.{svc}.{namespace} to configure all addresses. Add an option to use FQDN in all configs.
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 by locating the configuration paths that assemble service and pod addresses in the TiDB Operator. Compare the existing {svc}.{namespace} and {pod}.{svc}.{namespace} forms, then determine how an option could apply FQDN addressing consistently across all configurations. Done means the option affects every relevant configured address and its behavior is covered by the repository's tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100