search

kubernetes-sigs / controller-runtime

Repo for the controller-runtime subproject of kubebuilder (sig-apimachinery)
Apache License 2.0
2.41k stars 1.11k forks source link

Add chaos testing flags to controller runtime #1177

Open randomvariable opened 3 years ago

randomvariable commented 3 years ago

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

fejta-bot commented 3 years ago

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

randomvariable commented 3 years ago

/lifecycle frozen

camilamacedo86 commented 3 years ago

@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?