pingcap / pingcap/tidb-operator
Add E2E for PVC resize
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
For every component, add a case:
- Deploy a cluster.
- Scale-up storage size.
- After the storage request of PVC is changed, modify the capacity in status to mock expansion completed.
- Check all PVCs storage requests are changed.
- Check the StatefulSet is recreated.
Is your feature request related to a problem? Please describe:
Describe the feature you'd like:
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
The issue names no files or existing tests. Start by locating the current end-to-end coverage for cluster components, PVC changes, and StatefulSet recreation, then trace how PVC status is mocked. Done means each component has a resize case that verifies updated PVC requests and StatefulSet recreation after simulated expansion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100