[WIP] [Generated] Introduce preemption gates to workloads and add a single cluster preemption timeout configuration

[gizemo-bot]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This is an attempt to implement keps/8303-multikueue-orchestrated-preemption

Which issue(s) this PR fixes:

This is to understand the limits of code assistants as of today

Special notes for your reviewer:

This is a generated code, please review accordingly

Does this PR introduce a user-facing change?

NONE

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

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.

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue canceled.

Name	Link
🔨 Latest commit	152773a
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/6993203b7146e800086aa0f1

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: gizemo-bot / name: Gizem Özcan (152773a, a5b7386, e1167c9)
• ✅ login: kshalot / name: Karol Szuster (078d46b, 0e60f19, 0fef93f, 110621b, 182bb75, 192244e, 19dbba7, 292b1b1, 39e3ca4, 3a44862, 3b921f7, 3cadff7, 3da5ac3, 43ce21b, 4a6d9e9, 4b02865, 53bd86a, 6b2b2ce, 6ea9ad9, 71d7a7f, 7426363, 7c6548f, 804190f, 87d5867, 898bddd, 8adee7f, 92b5a6e, a6c82a9, b0ac348, b46add1, b858b5c, bdcc50c, be7e791, c1fde58, f042106, f0627c9, f9e74e6, fef809e)

[k8s-ci-robot]

Welcome @gizemo-bot!

It looks like this is your first PR to kubernetes-sigs/kueue 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kueue has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @gizemo-bot. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

Details

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gizemo-bot
Once this PR has been reviewed and has the lgtm label, please assign gabesaba for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[mimowo]

@kshalot we don't have yet a clear policy for commits co-authored by agents, could you for now open a PR on your behalf?

We need to figure this out, cc @tenzen-y @kannon92

[gizemo-bot]

@kshalot we don't have yet a clear policy for commits co-authored by agents, could you for now open a PR on your behalf?

We need to figure this out, cc @tenzen-y @kannon92

Hey sorry for the confusion, it is me Gizem playing around with this KEP. I'm not planning to merge this just checking the limits. And at the same time, it could be good to have a plan ready I guess, since soon we will face this kind of PRs

[kshalot]

@gizemo-bot Sidenote - maybe you can open a PR in the fork repo (https://github.com/gizemo-bot/kueue) instead of here. Then it won't be pinging any maintainers etc.

[gizemo-bot]

@gizemo-bot Sidenote - maybe you can open a PR in the fork repo (https://github.com/gizemo-bot/kueue) instead of here. Then it won't be pinging any maintainers etc.

Yes that was the plan which was not followed by the bot:) Should I move there, planning 1-2 more commits at most.

[tenzen-y]

@kshalot we don't have yet a clear policy for commits co-authored by agents, could you for now open a PR on your behalf?

We need to figure this out, cc @tenzen-y @kannon92

AFAIK, we previously brought this topic to the steering committee, but no decision has been made yet.