pingcap / pingcap/tidb-operator
Support to change configurations for only one pod in TiDB cluster
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:
Describe the feature you'd like:
Sometimes we hope to change args of only one pod to avoid rolling update the whole cluster.
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
The request does not identify files, tests, or an entry point. Start by examining the operator's existing cluster configuration and update behavior, then determine how a single pod could receive changed arguments without rolling the whole cluster. Done means the requested per-pod configuration is supported and the remaining pods are not unnecessarily rolled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100