pingcap / pingcap/tidb-operator
Automatically create PITR truncate CR
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:
The PITR truncate CR can only be created manually, while users may want to run the truncate periodically, requiring users to frequently create the truncate CR by hand.
Describe the feature you'd like:
Automatically create the PITR truncate CR based on the user-defined time intervals. For example, like auto truncate every 30 days?
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 locating the PITR truncate CR and the operator reconciliation entry points in this repository. Read how users currently create the CR and how time-based configuration is represented. Done means users can define an interval such as 30 days and the operator automatically creates truncate CRs on that schedule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, databases, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100