-
Notifications
You must be signed in to change notification settings - Fork 260
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
Prefix job workloads with job- #591
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mimowo The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
ab179d5
to
fdbbced
Compare
fdbbced
to
d3fa5e3
Compare
/assign @alculquicondor |
package common | ||
|
||
func GetNameForJob(jobName string) string { | ||
return "job-" + jobName |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can produce a name that is too long to pass validation. And if we cut the last characters we could have collisions. I would suggest using generateName
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, makes sense, then probably we can park it for now and only use generateName
for other frameworks, at least for now. WDYT?
Meaning we stay with the current workload naming for batch.Job.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sg
/close |
@mimowo: Closed this PR. In response to this:
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. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This is a preparatory task for #578. It is needed for avoiding workload name collisions created by different frameworks. The idea is that every framework will use a prefix for the workload name. The prefix for job will be "job-".
Which issue(s) this PR fixes:
Part of #65
Special notes for your reviewer:
The utility function is extracted to a separate package, which is not required for this task. However, it is used in the #578 PR to put it next to the analogous function for MPIJob. This way it is clear what is the list of prefixes in use.