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

NetworkPolicy scale tests #224

Closed
jianjuns opened this issue Dec 13, 2019 · 3 comments
Closed

NetworkPolicy scale tests #224

jianjuns opened this issue Dec 13, 2019 · 3 comments
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. proposal A concrete proposal for adding a feature

Comments

@jianjuns
Copy link
Contributor

Describe what you are trying to solve
Do scale tests and performance evaluation of Antrea NetworkPolicy implementation. This is mainly for NetworkPolicy computation and dissemination to Agents.

Describe the solution you have in mind
We need to cover:

  1. Controller NetworkPolicy computation performance and CPU/memory consumption.
  2. Controller to Agent dissemination.
    Odeally we should support the K8s scale of 5K Nodes.
    As a first step, we could start from 1K Nodes and 30K Pods, and at least verify Antrea does not perform very bad.

Describe the main design/architecture of your solution
As we might not be able to build a testbed with >1K Nodes and > 30K Pods, we might need some simulation here. Simulation of Nodes to stress Controller dissemination might be simple - we just need some concurrent clients to watch the NetworkPolicy resources from the Controller. Simulation of Pods and NetworkPolicies might require more work.

@jianjuns jianjuns added the proposal A concrete proposal for adding a feature label Dec 13, 2019
@jianjuns
Copy link
Contributor Author

@abhiraut @tnqn @weiqiangt

@jianjuns
Copy link
Contributor Author

jianjuns commented Mar 4, 2020

@tnqn and @weiqiangt: I am assigning this issue to you as you worked on the scale tests and already made some progress. Maybe you want to update the issue and add progress?

@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
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. proposal A concrete proposal for adding a feature
Projects
None yet
Development

No branches or pull requests

3 participants