Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simulated failures (aka chaos testing) in KIC tests #2787

Open
1 of 3 tasks
mflendrich opened this issue Aug 8, 2022 · 0 comments
Open
1 of 3 tasks

Simulated failures (aka chaos testing) in KIC tests #2787

mflendrich opened this issue Aug 8, 2022 · 0 comments

Comments

@mflendrich
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

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

  • 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant