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

Brainstorm enhancing UX #86

Closed
ahg-g opened this issue Mar 2, 2022 · 4 comments
Closed

Brainstorm enhancing UX #86

ahg-g opened this issue Mar 2, 2022 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@ahg-g
Copy link
Contributor

ahg-g commented Mar 2, 2022

We are adding more information to statuses of the various APIs we have (#7 and #5); but I am wondering what other UX-related enhancements we should pursue for the two personas: batch admin and batch user.

UX gets users excited about the system and I think should be a focal point as Kueue evolves.

@ahg-g ahg-g added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 2, 2022
@ArangoGutierrez
Copy link
Contributor

  • Prometheus integration for resource consumption of QueuedWorkloads / Queues

@ahg-g
Copy link
Contributor Author

ahg-g commented Mar 28, 2022

A kubectl plugin will be quite useful here for both admins and users.

@alculquicondor
Copy link
Contributor

I think we should update the QueuedWorkloadAdmitted condition to True in a best-effort basis.

This means that we don't need to do it in the scheduling cycle. But we can do it in the controller (we will get an event for the addition of the .spec.admission field).

@ahg-g
Copy link
Contributor Author

ahg-g commented Apr 10, 2022

Created #201 and #199 to track updating the workload condition and adding metrics. Closing this one.

@ahg-g ahg-g closed this as completed Apr 10, 2022
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

No branches or pull requests

3 participants