fix: scope pods' isolation problem (#1386) #1399
Merged
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 #1386 to release-1.1
You can switch your code base to this Pull Request by using git-extras:
# In chaos-mesh repo: git pr https://github.com/chaos-mesh/chaos-mesh/pull/1399
After apply modifications, you can push your change to this PR via:
Signed-off-by: Yue Yang g1enyy0ung@gmail.com
What problem does this PR solve?
This PR solves the pods' isolation problem between
normal scope pods
andnetwork target scope pods
.Before these changes, when you get any scope pods, the others will sync at the same time. This is unexpected behavior.
What is changed and how does it work?
Pods will not sync between scopes.
Checklist
Tests
Side effects
Related changes
Does this PR introduce a user-facing change?