Automated cherry pick of #5633: Check deletion event matches ClusterSet before Multi-cluster #5638
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When handling a ClusterSet deletion event in a member cluster, check the deleted ClusterSet and clean up Multi-cluster resources only when the current ClusterSet is deleted. Also fix and enhance the ClusterSet deletion unit test. Signed-off-by: Jianjun Shen <shenj@vmware.com>
tnqn
added
the
kind/cherry-pick
|
/test-multicluster-e2e |
luolanzone
approved these changes
Oct 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry pick of #5633 on release-1.14.
#5633: Check deletion event matches ClusterSet before Multi-cluster
For details on the cherry pick process, see the cherry pick requests page.