Conversation
efd4712 to
46ec0ef
Compare
46ec0ef to
bc42835
Compare
With the isolate action it is possible to block all inbound/outbound traffic to the host except for the loopback address and the list of allowed IP addresses specified in the action parameter.
This file contains hidden or 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
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.
What is the purpose of this PR / why it is needed?
With the isolate action, it is possible to block all inbound/outbound traffic to the host except for the loopback address and the
list of allowed IP addresses specified in the action parameter. For example, the below snippet defines an
isolateaction, that will block all incoming/outbound network traffic except for the172.17.0.4and8.8.8.8IP addresses, both remote and local destinations.What type of change does this PR introduce?
/kind feature (non-breaking change which adds functionality)
Any specific area of the project related to this PR?
/area rule-engine
Special notes for the reviewer
Does this PR introduce a user-facing change?
This PR brings a new feature that needs to be properly documented and communicated to the final users.