-
Notifications
You must be signed in to change notification settings - Fork 35
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 scalability tests #126
Comments
/priority p1 |
/priority p2 |
No eng resource assigned, priority 2 @xyhuang are you planning to take this on? if so, if you can assign yourself and please tag us so that PMs can add this to the kanban board |
/remove-priority p1 |
@chrisheecho sorry for the late response. I will try to implement this if I got time, but we might likely move it to 0.5, I agree to keep it as p2 for now. |
Let's try to have this for 0.5. A few things to consider:
What would it take for kubebench to support these?
|
@richardsliu here are some quick answers, we will discuss in more details: 1 & 2 agree, i will create a few issues to track required changes, they should be doable within 0.5. that being said, here are the needed things in my mind:
|
Let's split up the work. I can take care of item 1 (set up project, cluster, and Prow workflow). |
The Kubebench should be extended to support scalability tests in 2 ways:
It should also be able to collect metrics during the runs and make it easy to analyze the results, refer to #124 for this.
Also related with
kubeflow/training-operator#830
The text was updated successfully, but these errors were encountered: