add kep for clusterqueue exclude resource prefixes at ClusterQueue level

[kannon92]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Draft a KEP for ExcludeResources at the ClusterQueue level

Which issue(s) this PR fixes:

KEP for #5800

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name	Link
🔨 Latest commit	c19ba28
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/68ffceaacb04130008a89717
😎 Deploy Preview	https://deploy-preview-7415--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

[amy]

For Story 1, I guess... if you're allowing exclusions on the CQ level, let's take GPU as an example, where some CQs exclude GPU and some CQs don't.

You have multiple entry points to schedule GPUs. So the world view of the available nominalQuota in a Cohort doesn't necessarily match the underlying k8s cluster.

As in, the CQs that exclude GPUs can still schedule GPU workloads, thus taking up the underlying GPU in the cluster. But Kueue isn't tracking that. And then when other CQs try to claim that quota, its not actually there available to use.

[kannon92]

Yea good point. Talking with you offline I think maybe an allow list of resources may be a better choice than adding this at CQ.

This would put more work on a cluster admin actually and could potentially lead to people skipping kueue resourcing.

[kannon92]

/close

[k8s-ci-robot]

@kannon92: Closed this PR.

In response to this:

/close

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.