kubernetes-sigs / kubernetes-sigs/controller-runtime
Add chaos testing flags to controller runtime
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3k
- Forks
- 1.3k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 14
Description
User Story
As a Cluster API developer I would like to discover bugs. In particular, I want to know if my controllers are properly re-entrant.
Detailed Description
It'd be great to add a --chaos or similar flag that will deliberately exit CR after a random amount of time. This would allow downstream consumers to do more testing as to controller re-entrancy
Anything else you would like to add:
/kind feature
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 with CONTRIBUTING.md and its CAEP guidance, then locate the controller runtime's command-line flag setup and process entry point. Done means a chaos-related flag can deliberately terminate the controller after a random interval, enabling downstream re-entrancy testing; the issue does not name a test file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100