- 
                Notifications
    You must be signed in to change notification settings 
- Fork 23
Feat nftables #346
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
Feat nftables #346
Conversation
b09cab5    to
    1d39829      
    Compare
  
    Add nftables support for egress NAT functionality temp: enable CI for this branch Add nftables usage logging to coil-egress initialization Improve enable-nft flag description to clarify NAT backend choice Add nftables manifest Add coil nftables test Add nftables to Dockerfile Remove iptables CHECKSUM rules from FoU tunnel initialization add mac support Add Mac support to setup-echotest Add support multi platform Add EnableNFT field to Egress CRD Add nftables E2E test support Remove unnecessary kube-proxy double NAT workaround Add counter expressions to nftables rules in egress add cross-platform support for yq binary download Fix crd manifest generation in Makefile Update generated CRDs to controller-gen v0.18.0 Run garbage collection immediately without waiting for first tick refactor: use timer instead of ticker in garbage collector ci: remove support-nftables branch trigger
Signed-off-by: Tomoki Sugiura <tomoki-sugiura@cybozu.co.jp>
1d39829    to
    67f9594      
    Compare
  
    Signed-off-by: Tomoki Sugiura <tomoki-sugiura@cybozu.co.jp>
| I think we need add following contents about this changes. 
 | 
Signed-off-by: Tomoki Sugiura <tomoki-sugiura@cybozu.co.jp>
| 
 It seems  | 
| @chez-shanpu | 
Signed-off-by: Tomoki Sugiura <tomoki-sugiura@cybozu.co.jp>
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
| @Till0196 Finally, nftables feature is merged! Thank you for your contribution!! | 
Follow up #345