You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's sufficient for a controller (like kueue) which watches every Workload object and is able to maintain an index.
OTOH, a CLI would have to call List and filter client-side to find the corresponding workload. A label allows to do the filtering server-side.
What would you like to be added:
The name of a Workload doesn't match the name of the Job, to avoid collisions among different CRDs.
As a result, it's hard to quickly obtain the Workload for a particular job. A pair of labels (for name and GVK) would make it feasible to query.
Why is this needed:
For general usability and also to efficiently implement a CLI that gives you all relevant information for a job #487
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered: