-
Notifications
You must be signed in to change notification settings - Fork 206
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
Add configurability to Netavark firewall driver #1750
Conversation
35fe3a7
to
c94c5b4
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.
You also have to add this new field to docs/containers.conf.5.md to documented it in the man page.
b8e08af
to
8bceee8
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.
You still have to document the field under docs/containers.conf.5.md
pkg/config/containers.conf
Outdated
# The default firewall driver to be used | ||
# firewall_driver = "iptables" |
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.
# The default firewall driver to be used | |
# firewall_driver = "iptables" | |
# The firewall driver to be used by netavark. | |
# The default is empty which means netavark will pick one accordingly. Current supported | |
# drivers are "iptables", "none" (no firewall rules will be created) and "firewalld" (firewalld is | |
# experimental at the moment and not recommend outside of testing). In the future we are | |
# planning to add support for a "nftables" driver. | |
#firewall_driver = "" |
As text for the documentation. @mheon WDYT?
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.
Should mention that the default is iptables - maybe "Netavark will use the default (iptables)" instead of "netavark will pick one accordingly"
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.
Yeah I was thinking about it but then I remembered that we do not really control what nv version is on the system and if we decide to flip the default to nftables once it is ready I would assume that we forget to update the page here.
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.
Fair enough. We might also add some sort of autodetection for systems without iptables but with nft at some point as well, which would affect the default.
8bceee8
to
c5e03a5
Compare
closes containers#1338 Signed-off-by: Chetan Giradkar <[email protected]>
c5e03a5
to
e8d080d
Compare
@cgiradkar is this still a draft? |
LGTM |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgiradkar, Luap99 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 |
closes #1338