pingcap / pingcap/tidb-operator
Optimize the output of backup crd
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Two request：
-
The overall progress of the BR backup cannot be seen using the operator backup, but the progress can be seen by using the br tool backup directly. I hope this output can be optimized.
-
In addition, can the display column of bks have more information, (such as
If maxbackup and maxReservedTime are set at the same time, maxReservedTime shall prevail, but only maxbackup is shown here, which will cause misunderstanding)
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 operator backup output for the BR backup and the bks display column, then compare it with the progress shown by the BR tool directly. Done means the operator exposes overall backup progress and clearly shows whether maxReservedTime takes precedence over maxbackup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100