Consider adding a scalability-5k-presubmit pool

[BenTheElder]

x-ref: kubernetes/test-infra#34546 (comment)

Also we should revisit with sigs.k8s.io/prow about restricted triggering for presubmits similar to restricted rerun permission for periodic/postsubmit, since these jobs are ripe for abuse.

/sig scalability testing k8s-infra

cc @serathius

[BenTheElder]

Also we should revisit with sigs.k8s.io/prow about restricted triggering for presubmits similar to restricted rerun permission for periodic/postsubmit, since these jobs are ripe for abuse.

starting that in slack, pending discussion will file and cross link a github issue in prow ...

https://kubernetes.slack.com/archives/CDECRSC5U/p1742851876219149

[BenTheElder]

Last time we added one: #3221 #2195

#2195 (comment)

[BenTheElder]

I think this one is pretty manual, we can do a semi-automated GCP project addition but then we need to get all the appropriate quotas, we can probably just assume the quotas from the periodic job should be requested on the new one.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[xmudrii]

/remove-lifecycle rotten