pingcap / pingcap/tidb-operator
A way to check if state is "dirty" on TidbCluster CRD
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:
After applying a change to a TidbCluster CRD, I'd like to be able to check whether the cluster state is in-sync. At the moment, status.conditions[0] remains in the "Ready" state. Individual components' phase eventually becomes Upgrading, but due to the delay the values cannot be used to wait on.
Describe the feature you'd like:
I'd like some state under status to change synchronously when a change is applied to the TidbCluster CRD. That way I can immediately monitor that value after the change is made.
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 inspecting the TidbCluster CRD status and the controller reconciliation path to understand when status conditions and component phases change. Define a synchronous status indicator for configuration changes, then verify that it changes immediately after applying a CRD update and can be monitored until the cluster is in sync.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100