-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libnetwork/netavark: add isolate option 'strict' #1513
libnetwork/netavark: add isolate option 'strict' #1513
Conversation
accde5a
to
55f56c1
Compare
55f56c1
to
1979b54
Compare
@Luap99 PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@vrothberg PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A unit test for the function would nice.
May i add |
Yes, |
The strict isolate refuses to communicate with non-isolate and isolate. Signed-off-by: Saigusa Yasushi <[email protected]>
1979b54
to
238885e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you.
@Luap99 PTAL
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99, vrothberg, yassi-github The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
The isolation is only enabled when both bridges are in
--opt isolate=true
mode.This means it is possible to communicate with non-isolated and isolated.
So we adds
--opt isolate=strict
option to deny communication, even with non-isolated and isolated.Passing this option to netavark creates iptables rules for strict isolation.