Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[clusterQueue] Keep different counters of reserved and in use resources in the queues status. #1195

Closed
3 tasks
trasc opened this issue Oct 11, 2023 · 4 comments · Fixed by #1206
Closed
3 tasks
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@trasc
Copy link
Contributor

trasc commented Oct 11, 2023

What would you like to be added:
Different counters of reserved and in use resources in the queues status.

Why is this needed:

To be able to check the difference between the quota that is reserved and the one that is reserved and workload admitted. In a tow stem admission scenario.

Completion requirements:

This enhancement requires the following artifacts:

  • Design doc
  • API change
  • Docs update

The artifacts should be linked in subsequent comments.

@trasc trasc added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 11, 2023
@trasc
Copy link
Contributor Author

trasc commented Oct 11, 2023

/assign

@trasc trasc closed this as completed Oct 11, 2023
@trasc
Copy link
Contributor Author

trasc commented Oct 11, 2023

/reopen

@k8s-ci-robot
Copy link
Contributor

@trasc: Reopened this issue.

In response to this:

/reopen

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.

@k8s-ci-robot k8s-ci-robot reopened this Oct 11, 2023
@trasc
Copy link
Contributor Author

trasc commented Oct 11, 2023

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants