pingcap / pingcap/tidb-operator
Add a protection mechanism to prevent accidental deletion of TC
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:
Due to human operation, TC was deleted by mistake
Describe the feature you'd like:
If there are some tips or a second confirmation, it will be better.
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 by tracing how the operator handles deletion of TC resources and identify the relevant Kubernetes reconciliation entry points. Clarify whether protection should use a warning, a second confirmation, or another mechanism, and define the expected behavior before implementation; done means accidental deletion is prevented and the behavior is documented and tested.
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
- 25/100