contrib/k8s: Add 'nsexec' script to run commands in the network namespace of a POD #14361
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
…pace of a POD Add script 'nsexec' for running commands in the network namespace of a k8s POD. This is useful for inspecting and debugging the networking configuration within a pod, or originating traffic from a POD without needing to install 'curl' in there, for example. Currently this relies on Docker being the container runtime. Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
jrajahalme
added
area/misc
|
This is a new script not being used by default, so running the CI is not necessary. |
joestringer
approved these changes
Dec 10, 2020
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.
Add script 'nsexec' for running commands in the network namespace of a
k8s POD. This is useful for inspecting and debugging the networking
configuration within a pod, or originating traffic from a POD without
needing to install 'curl' in there, for example.
Currently this relies on Docker being the container runtime.
Signed-off-by: Jarno Rajahalme jarno@covalent.io