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

Enhance troubleshooting to understand if a job is actually running #2154

Open
1 of 3 tasks
alculquicondor opened this issue May 7, 2024 · 2 comments
Open
1 of 3 tasks
Assignees
Labels
kind/documentation Categorizes issue or PR as related to documentation.

Comments

@alculquicondor
Copy link
Contributor

alculquicondor commented May 7, 2024

What would you like to be added:

This question just refers to whether the job is suspended https://kueue.sigs.k8s.io/docs/tasks/troubleshooting/troubleshooting_jobs/#is-my-job-running

In some cases, the suspend field can be false, while the pods are unschedulable.

It would be useful to make the distinction.

Why is this needed:

Users don't necessarily understand the separation of concerns between kueue and kube-scheduler or cluster-autoscaler. We need to direct them to ask the right questions.

Completion requirements:

This enhancement requires the following artifacts:

  • Design doc
  • API change
  • Docs update

The artifacts should be linked in subsequent comments.

@alculquicondor alculquicondor added the kind/feature Categorizes issue or PR as related to a new feature. label May 7, 2024
@tenzen-y
Copy link
Member

tenzen-y commented May 9, 2024

/remove-kind feature
/kind documentation

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. and removed kind/feature Categorizes issue or PR as related to a new feature. labels May 9, 2024
@alculquicondor
Copy link
Contributor Author

/assign

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

No branches or pull requests

3 participants