-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Automated cherry pick of #44108 #44290
Automated cherry pick of #44108 #44290
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.
The 'parent' PR of a cherry-pick PR must have one of the "release-note" or "release-note-action-required" labels, or this PR must follow the standard/parent release note labeling requirement. (release-note-experimental must be explicit for cherry-picks) |
@k8s-bot gce etcd3 e2e test this |
Does this fix a regression or broken use case? If so, please explain or link to the bug. |
This fixes a bug in federation cascading deletion. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nikhiljindal, shashidharatd
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue |
…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). ```
Cherry pick of #44108 on release-1.6.
#44108: fed: Disable orphaning of per-cluster resources on deletion.