Add info to ClusterQueue status

[ahg-g]

Suggestions:

• admitted workloads
• pending workloads
• Capacity allocated
• Capacity borrowed

/kind feature

[alculquicondor]

/assign

[ahg-g]

Should we add pending workloads to capacity as well?

[alculquicondor]

Aggregating the sizes of all the queues pointing to it? We should be able to implement that efficiently, but could it be confusing?

[ahg-g]

Why would it be confusing? The pending workloads at a queue level isn't really that useful i would say for an admin to look at compared to an aggregated view at the capacity level

[alculquicondor]

/reopen

Sounds good. Although I will tackle this after #80 (comment)

[k8s-ci-robot]

@alculquicondor: Reopened this issue.

In response to this:

/reopen

Sounds good. Although I will tackle this after #80 (comment)

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.

[ArangoGutierrez]

I strongly disagree with

The pending workloads at a queue level isn't really that useful

For users, is the most important after deploying, if queues are going to be a user managed object, we need to provide as much valuable information to them at the namespace lvl.

As an admin all I care is big numbers and usage. I think we are looking at this with an admin/cloud provider point of view and not from the end user.

we need to think as a cascade here

CQ -> Q -> QW

[ArangoGutierrez]

pending workloads at a queue level are one of THE most important reasons why people want to have a queuing mechanism in kubernetes.

[ArangoGutierrez]

/retitle Add info to ClusterQueue status

[ahg-g]

sg, I already proposed a way to track the number of admitted workloads at Q level

[ahg-g]

oh, you are referring to the count of pending workloads; I guess I agree in general the the more info we can surface the better

[xieydd]

I agree with the comment from @ArangoGutierrez .
Considering the cascade of CQ, Q and QW, we need the more info we can of workload , we can aggregate some info for Q and CQ.

[ahg-g]

sg, then with regards to this issue we need two things in CQ status:

• Rename AssignedWorkloads to AdmittedWorkloads
• Pending workloads

/help
/unassign @alculquicondor

[k8s-ci-robot]

@ahg-g:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

sg, then with regards to this issue we need two things in CQ status:

• Rename AssignedWorkloads to AdmittedWorkloads
• Pending workloads

/help
/unassign @alculquicondor

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.

[ArangoGutierrez]

sg, then with regards to this issue we need two things in CQ status:

• Rename AssignedWorkloads to AdmittedWorkloads
• Pending workloads

/help /unassign @alculquicondor

Check first one #110

[ArangoGutierrez]

For Pending workloads do we still want to track that on kueue.clusterqueue.Status?
as it is right now, a workload has to be admitted into a clusterqueue, so to the eyes of clusterqueue it is never pending, pending feels better at the kueue.queue lvl, tracking workloads that have not yet been admitted, right?
if yes we can close this issue as done, and focus on #5 only

[alculquicondor]

Pending workloads are the workloads that are still in the heap, so they haven't been admitted.

Yes, we should add that field to clusterQueue.status

[ahg-g]

/close

[k8s-ci-robot]

@ahg-g: Closing this issue.

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