pingcap / pingcap/docs-tidb-operator
Need detailed steps on this recovery
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 52
- Forks
- 129
- Avg merge
- 12m
- Merged PRs (30d)
- 2
Description
File: /release-1.0/en/troubleshoot.md
If a StorageClass exists in the cluster but the available PV is insufficient, you need to add PV resources correspondingly.
How? The PV is supposed to be managed by tidb-operator, how can we manually add it and let tidb-operator honor it?
Contributor guide
No contributing guide indexed for this repository
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 release-1.0/en/troubleshoot.md and the quoted recovery guidance. Verify how tidb-operator handles StorageClass and PV resources, then document the manual PV steps and the configuration needed for the operator to honor them. Done means the recovery procedure is explicit and actionable for a Kubernetes user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100