-
Notifications
You must be signed in to change notification settings - Fork 2.8k
add 5000 node dra test #35590
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
add 5000 node dra test #35590
Conversation
|
/assign @wojtek-t |
30d36cc to
2092ddd
Compare
2092ddd to
dd97e1b
Compare
7c96747 to
a0bb5f4
Compare
|
/hold |
| - --env=KUBE_DNS_MEMORY_LIMIT=300Mi | ||
| - --extract=ci/fast/latest-fast | ||
| - --gcp-nodes=5000 | ||
| - --gcp-project-type=scalability-scale-project |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are only one of these projects currently, this job would have to be deconflicted with the existing 5k node jobs
| - "perfDashBuildsCount: 270" | ||
| - "perfDashJobType: performance" | ||
| # TODO (alaypatel07): increase this interval once stable | ||
| interval: 12h |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we almost certainly need to use a cron to avoid scheduling conflicts, and also not increase the interval, these are really expensive, and it requires some time to coordinate permission for quota this large in a project without a contract 🙃
|
what prevents us from including DRA in any of the existing 5k node jobs? we spend a lot of time and resources just doing things like dumping all of the logs to storage |
There is a sense of not disrupting the stability of existing 5k node jobs with a new job, since those are release informing and monitored very closely. |
a0bb5f4 to
7cd2a5e
Compare
|
/assign wojtek-t marseel |
|
/lgtm from DRA perspective |
6deaebb to
e2ab4e8
Compare
|
@BenTheElder @jackfrancis the release blocking jobs run on odd days: test-infra/config/jobs/kubernetes/sig-scalability/sig-scalability-release-blocking-jobs.yaml Line 74 in e2ab4e8
I have configured this job to run on even days, 9:01 AM EST. Please look if this work and approve/lgtm so we can get unblocked here |
|
/hold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alaypatel07, jackfrancis The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
e2ab4e8 to
37726aa
Compare
|
/hold cancel |
Signed-off-by: Alay Patel <[email protected]>
37726aa to
34b78d9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
@alaypatel07: Updated the
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
This test exercises the dra test for 5000 node test.
It is created as a separate test for checking the stability, eventually it will be merged into the release informing tests and this test will be removed to save infrastructure costs.