-
Notifications
You must be signed in to change notification settings - Fork 254
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
[kjobctl] Skip kueue labels on child objects. #3455
base: main
Are you sure you want to change the base?
[kjobctl] Skip kueue labels on child objects. #3455
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mbobrovskyi 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 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
cc @mwysokin |
@@ -190,6 +190,26 @@ func (b *slurmBuilder) validateMutuallyExclusiveFlags() error { | |||
return nil | |||
} | |||
|
|||
func (b *slurmBuilder) buildObjectMeta(templateObjectMeta metav1.ObjectMeta) metav1.ObjectMeta { | |||
objectMeta := b.Builder.buildObjectMeta(templateObjectMeta) | |||
objectMeta.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.
This looks strange, maybe b.Builder.buildObjectMeta(templateObjectMeta)
should not set GeneratName if it's not generally useful.
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.
It’s used in other modes. Only Slurm no need it for now.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
We don't need to add kueue labels to child objects like ConfigMap or Service.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?