pingcap / pingcap/tidb-operator
e2e: dump logs before killing tidb-operator pods
Open
Nobody has claimed this yet.
lifecycle/stale
status/help-wanted
test/e2e
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
With operator killer enabled, logs of deleted pods in e2e are not collected. We should collect logs for them too.
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 e2e flow that enables the operator killer and deletes TiDB-operator pods, then inspect how logs are currently collected. Done means logs from pods targeted for deletion are captured before they are killed and included in the e2e output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100