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

Support scale testing framework for network policies #464

Closed
jayunit100 opened this issue Mar 4, 2020 · 2 comments
Closed

Support scale testing framework for network policies #464

jayunit100 opened this issue Mar 4, 2020 · 2 comments
Labels
enhancement New feature or request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@jayunit100
Copy link
Contributor

Describe the problem/challenge you have

Netpol framework is hardcoded to a/b/c x/y/z

Describe the solution you'd like

Would like to test larger scales of , for example, 30 pods per node. and possibly use

  • fuzz testing to ensure breadth of coverage : generate policy and back calculate expectations
  • psuedo-random verification for performance: reducing probe test coverage (so that we dont wind up sending out 10000s of probes in a large cluster.)

Anything else you would like to add?

discussed in antrea community meeting with @antoninbas and others.

cc @jianjuns can we use this to implement #224 ? Would be cool to merge streams

@jayunit100 jayunit100 added the enhancement New feature or request label Mar 4, 2020
@abhiraut abhiraut changed the title Support scale for network policies Support scale testing framework for network policies Mar 4, 2020
@jianjuns
Copy link
Contributor

jianjuns commented Mar 4, 2020

cc @jianjuns can we use this to implement #224 ? Would be cool to merge streams

Would like @tnqn and @weiqiangt to comment too, as they worked on our current scale tests. In general I would agree always good to share the framework for tests. But #224 created by me also includes some simulation (of Nodes and Pods) part.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 1, 2020

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment, or this will be closed in 180 days

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants