-
Notifications
You must be signed in to change notification settings - Fork 29
force delete crd work after deleting condition is true #753
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
force delete crd work after deleting condition is true #753
Conversation
68abd4c to
fdcb544
Compare
|
/assign @qiujian16 |
5a39e2c to
cc838df
Compare
| if works.Items[0].DeletionTimestamp.IsZero() { | ||
| crdWork := works.Items[0] | ||
| if crdWork.DeletionTimestamp.IsZero() { | ||
| return r.clientHolder.WorkClient.WorkV1().ManifestWorks(cluster.Name). |
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 recall that the registration controller is responsible for deleting this ManifestWork. Why is the import-controller also deleting it?
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.
you are right. do not need delete again here.
fixed.
cc838df to
082cdeb
Compare
| if crdWork.DeletionTimestamp.IsZero() || | ||
| !meta.IsStatusConditionTrue(crdWork.Status.Conditions, workv1.WorkDeleting) { |
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 believe !meta.IsStatusConditionTrue(crdWork.Status.Conditions, workv1.WorkDeleting is sufficient. What do you think?
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.
yes. fixed.
Signed-off-by: Zhiwei Yin <[email protected]>
082cdeb to
77a269c
Compare
|
/lgtm |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elgnay, qiujian16, zhiweiyin318 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 |
|
/unhold |
|
d192672
into
stolostron:main
|
/cherry-pick backplane-2.9 |
|
@elgnay: new pull request created: #801 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-sigs/prow repository. |



No description provided.