You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our e2e tests should try to mimic a production lifecycle of components within the cluster, the controller, and the proxy. We should introduce chaos (chaos testing) to simulate production cluster problems.
Proposed Solution
tests of our APIs in the e2e environment should be pointed at real applications (e.g. not httpbin) doing validated work
the cluster should have its resources exhausted at various points, semi-arbitrarily
the cluster network should be saturated at various points
nodes should be randomly killed without warning during the tests
Additional information
Broken out of #1605 originally reported by @shaneutt.
This issue is a rewrite that narrows down the scope and indicates the experimental nature of this enhancement.
Acceptance Criteria
A suite of chaos-induced tests is defined, possibly inspired by/extending the above, and documented on this issue or in a KEP/design doc.
Issues for individual planned test cases are created.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Problem Statement
Our e2e tests should try to mimic a production lifecycle of components within the cluster, the controller, and the proxy. We should introduce chaos (chaos testing) to simulate production cluster problems.
Proposed Solution
httpbin
) doing validated workAdditional information
Broken out of #1605 originally reported by @shaneutt.
This issue is a rewrite that narrows down the scope and indicates the experimental nature of this enhancement.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: