controller-runtime icon indicating copy to clipboard operation
controller-runtime copied to clipboard

Add chaos testing flags to controller runtime

Open randomvariable opened this issue 5 years ago • 3 comments

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

randomvariable avatar Sep 25 '20 16:09 randomvariable

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot avatar Dec 24 '20 17:12 fejta-bot

/lifecycle frozen

randomvariable avatar Jan 04 '21 14:01 randomvariable

@vincepri,

Is not it blocker by Cluster API implementation? So, could we not add here the label triage/blocked as well and maybe help wanted?

camilamacedo86 avatar Jan 26 '21 17:01 camilamacedo86