-
Notifications
You must be signed in to change notification settings - Fork 299
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
[kueuectl] Delete the corresponding Job when deleting a Workload. #2992
[kueuectl] Delete the corresponding Job when deleting a Workload. #2992
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
1ae5e21
to
3df829a
Compare
/cc @trasc |
919c219
to
db42b2e
Compare
5c70290
to
c98e7b0
Compare
/assign @mwielgus |
c98e7b0
to
b5330e4
Compare
d8d7a32
to
ac495ed
Compare
return workloads, haveAssociatedWorkloads, nil | ||
} | ||
|
||
func (o *WorkloadOptions) getWorkloadResources(workloads []*v1beta1.Workload) (map[*v1beta1.Workload][]GroupVersionResourceName, error) { |
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.
Maybe we should not put too much pressure on this now but, the first owner may not be the actual (root) owner of the wl for example in case of FluxMiniclusters, deployments and probably more, both the fist layer owner and the workload will be recreated.
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 is a good point! We can address the root owner and delete it. However, a deployment can create multiple workloads. Deleting the deployment will also remove all associated workloads.
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.
To ensure we do not lose context, let's continue the discussion at #3101 (comment).
Can you either split the PR or add description what else, apart from delete, is being done there and why these changes need to go together? |
e76d799
to
4f9f9c6
Compare
bc44b76
to
d890daa
Compare
/hold |
072be2d
to
d849ae0
Compare
Co-authored-by: Traian Schiau <traian_schiau@epam.com>
882ea4a
to
15c5642
Compare
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.
/lgtm
LGTM label has been added. Git tree hash: 8dcd275020e00ad1fe0d52ec4068bc2f3d28afd9
|
/approve
I believe since Marcin lgtm'ed the KEP we are good to go. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mbobrovskyi, mimowo The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…bernetes-sigs#2992) * Delete the corresponding Job when deleting a Workload. * Fix workload completion func. * Add delete confirmation. * Allow to delete all workloads. * Use unit tests instead integration. * Ignore out for delete all workloads. * Fix typos. * Remove unnecessary resources on unit-tests. * Fixes accordingly to the KEP updates. * Rephrase description. Co-authored-by: Traian Schiau <traian_schiau@epam.com> * Delete cascade strategy. --------- Co-authored-by: Traian Schiau <traian_schiau@epam.com>
What type of PR is this?
/kind bug
What this PR does / why we need it:
WorkloadNameFunc
to allow autocompletion for multiple resource names in arguments.Which issue(s) this PR fixes:
Fixes #2975
Special notes for your reviewer:
Does this PR introduce a user-facing change?