-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
[Federation] Use cascading deletion when deleting resources in underlying clusters #44108
Conversation
The Federation control plane issues a delete command unless it wants to orphan the underlying per-cluster resource. When issuing that command, always set the orphanDependents to false.
/release-note-none |
Thanks lgtm. I wasnt expecting the kubefed change, but should be fine. I can cherrypick this with my PR. Will also run e2e once to make sure that its WAI :) |
Verified that e2e tests pass with this change. /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: csbell, nikhiljindal
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
Commit found in the "release-1.6" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
…y-pick-of-#44108-upstream-release-1.6 Automatic merge from submit-queue Automated cherry pick of kubernetes#44108 Cherry pick of kubernetes#44108 on release-1.6. kubernetes#44108: fed: Disable orphaning of per-cluster resources on deletion. ```release-note Fix for [federation failing to propagate cascading deletion](kubernetes#44304). ```
The Federation control plane issues a delete command unless it wants to orphan the underlying per-cluster resource. When issuing that command, always set the orphanDependents to false.
/release-note-none
/sig-federation