delay pod creation feature not consider resourcequota

[merryzhou]

/kind feature

As mentioned in delay pod design, scheduler should watch resourcequota to decide whether podGroup has enough resource quota to create.

Quota
To delay pod creation, both kube-batch and PodGroupMinResources will watch ResourceQuota to decide which PodGroup should be in queue firstly. The decision maybe invalid because of race condition, e.g. other controllers create Pods. In such case, PodGroupMinResources will reject PodGroup creation and keep InQueue state until kube-batch transform it back to Pending. To avoid race condition, it's better to let kube-batch manage Pod number and resources (e.g. CPU, memory) instead of Quota

But now in the implementation, the enqueue action controls the quota by queue.Spec.Capability instead of k8s resourcequota, so I am curious about the reason why not use resourcequota to control quota。 Is there any consideration？

Environment:

• Volcano Version: v0.4.2

[hzxuzhonghu]

The queue is cluster scoped not namespace scoped, and it is a set of podgroups in different namespaces. And different queues can include podgroups of the same namespaces too.

As the resourcequota, it is the kube-apiserver that use it to intercept the pod creation

[k82cn]

scheduler should watch resourcequota to decide whether podGroup has enough resource quota to create.

+1, it's better to avoid enquing an PodGrouop which does not have enough quota :)

Would you like to create a PR for that?

[merryzhou]

Would you like to create a PR for that?

ok，I‘d like to have a try.

[stale]

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

[stale]

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗

[k82cn]

Let's keep this issue open :)

[stale]

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

[stale]

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗