Increase the Resources for pull-verify-kueue-main

[Vandit1604]

The verify job takes more than ~15 mins to complete, which adds more time to the release process. This is an attempt to check if increasing the resources for verify job reduces the time.

See for more info: kubernetes-sigs/kueue#1849

[k8s-ci-robot]

Hi @Vandit1604. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[kannon92]

Can you look at the dashboards and see if we are hitting close to these limits?

[kannon92]

/ok-to-test

[kannon92]

/lgtm

I couldn't find the dashboard for kueue. Its only 4 cores so I think its worth a shot.

[kannon92]

/assign @alculquicondor @mimowo

[BenTheElder]

you should probably allocate comparable memory?

1.5gi/core is pretty low, I'd aim for 2gi/core to start.

---

cc @mahamed @xmudrii interesting optimization problem: some jobs may be going slower due to artificially memory limiting themselves while still creating a cluster scaling bottleneck around allocated cores.

we should consider enforcing a core:mem limit to simplify this and make expectations more uniform between the EKS/GKE build clusters

[BenTheElder]

recurring topic #32315 (comment)

[alculquicondor]

Please set the memory to 8Gi, as recommended

[Vandit1604]

Done.

[alculquicondor]

Can you look at the dashboards and see if we are hitting close to these limits?

kubernetes-sigs/kueue#1849 (comment)

[Vandit1604]

Link to the dashboard: https://monitoring-eks.prow.k8s.io/d/96Q8oOOZk/builds?orgId=1&from=now-7d&to=now&var-org=kubernetes-sigs&var-repo=kueue&var-job=pull-kueue-test-integration-main&var-build=All&refresh=30s

cc: @kannon92

[alculquicondor]

/ok-to-test
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alculquicondor, Vandit1604

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:

• config/jobs/kubernetes-sigs/kueue/OWNERS [alculquicondor]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kannon92]

@Vandit1604 thanks for sharing! I'm happy with this change given the discussion. Feel free to merge!

[Vandit1604]

The failing tests looks unrelated to the changes in this PR or maybe I'm missing something here (?)

[alculquicondor]

/retest

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[k8s-ci-robot]

@Vandit1604: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key kueue-presubmits-main.yaml using file config/jobs/kubernetes-sigs/kueue/kueue-presubmits-main.yaml

In response to this:

The verify job takes more than ~15 mins to complete, which adds more time to the release process. This is an attempt to check if increasing the resources for verify job reduces the time.

See for more info: kubernetes-sigs/kueue#1849

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/test-infra repository.

[alculquicondor]

Just FYI: This actually helped to reduce the runtime to almost half :)