pingcap / pingcap/tidb-operator
avoid user directly delete a cluster already join a cross-Kubernetes 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:
https://docs.pingcap.com/tidb-in-kubernetes/dev/deploy-tidb-cluster-across-multiple-kubernetes#exit-and-reclaim-clusters-that-already-join-a-cross-kubernetes-cluster
avoid user directly delete a cluster already join a cross-Kubernetes cluster
currently, you must scale all component' replicas as 0 before deleting the tc or if will just like stoping all component if you delete the tc directly.
Describe the feature you'd like:
forbid to delete a joined cluster if the replica of some component is not 0
or
do scale in when handling the delete tc
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 linked cross-Kubernetes cluster documentation, especially the exit and reclaim workflow, and trace the operator's handling of deleting a joined TC. Compare the two proposed outcomes—rejecting deletion when any component replica is nonzero or scaling components in during deletion—and define completion around safe cluster removal without merely stopping components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100