Use "ip netns exec" instead of "nsenter" to handle pod restart in network-chaos but for 2.14.X #703
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.
This PR is duplicate of #702 but for 2.14.X
What this PR does / why we need it:
Updating network-chaos to use the netns instead of the procedure to inject/remove chaos so the network-chaos can handle pod restart.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #591Special notes for your reviewer:
I think this PR will need "requires-upgrade".
Checklist:
breaking-changes
tagrequires-upgrade
tag