What would you like to be added:
I would like to provide the validation feature for all Jobs without queue-name (requiredJobsWithQueueName), which rejects the Jobs without queue-name.
However, the validations will be implemented as VAPs, and we never implement the custom validation mechanism as webhook and other APIs.
If the cluster administrator enables the requiredJobsWithQueueName in the Kueue Configuration API, the kueue-controller-manager will create the VAPs for all enabled Jobs.
Why is this needed:
The manageJobsWithoutQueueName automatically suspends all Jobs without queue-name to avoid the quota violation.
But the feature does not have good UX since it's challenging for batch users to find the reason why their Jobs are not runnable.
So, I would like to provide a way that they can easily find the reason when they submit Jobs.
Completion requirements:
This enhancement requires the following artifacts:
[x] Design doc
[ ] API change
[ ] Docs update
The artifacts should be linked in subsequent comments.
What would you like to be added: I would like to provide the validation feature for all Jobs without queue-name (
requiredJobsWithQueueName
), which rejects the Jobs without queue-name. However, the validations will be implemented as VAPs, and we never implement the custom validation mechanism as webhook and other APIs.If the cluster administrator enables the
requiredJobsWithQueueName
in the Kueue Configuration API, the kueue-controller-manager will create the VAPs for all enabled Jobs.Why is this needed: The manageJobsWithoutQueueName automatically suspends all Jobs without queue-name to avoid the quota violation. But the feature does not have good UX since it's challenging for batch users to find the reason why their Jobs are not runnable.
So, I would like to provide a way that they can easily find the reason when they submit Jobs.
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.