pingcap / pingcap/tidb-operator
Need to expose readiness probe for PD in TidbCluster spec
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:
Related to https://github.com/tikv/pd/issues/5658. During the rolling upgrade of PD, raft index lag could lead to the PD cluster being unavailable. Readiness check could make PD cluster keep a quorum of voting members up during the rolling update.
Describe the feature you'd like:
We want to expose a readiness probe for PD in the TidbCluster spec.
Describe alternatives you've considered:
We could hardcode logic for adding readiness probes for PD, but it would be nice to give flexibility to the users.
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 by locating the TidbCluster spec and tracing how its fields are rendered into the PD Kubernetes resources. Define how users configure the PD readiness probe, then verify the generated resources and relevant tests reflect that configuration.
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
- Mostly clear
- Newbie friendliness
- 35/100