pingcap / pingcap/tidb-operator
Add ServiceSpec for TiKV and Discovery 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
Currently we can specify ServiceSpec in many components but not tikv services, does it make sense to add ServiceSpec for TiKV and discovery configurations?
Is your feature request related to a problem? Please describe:
Describe the feature you'd like:
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
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 the ServiceSpec API reference in docs/api-references/docs.md and compare how ServiceSpec is exposed for the existing components. Then identify the TiKV and discovery configuration definitions and determine the intended API shape; done means the design is agreed and the API reference reflects the supported configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100