We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
By default Linux has filter table FORWARD chain has default policy as DROP.
filter
FORWARD
DROP
Its actually policy by Docker 1.13 moby/moby#28257
Some possible options for CNI plugins kubernetes/kubernetes#40182
I guess Kube-router should add exception atleast to permit the traffic from kube-bridge interface
kube-bridge
iptables -A FORWARD -o kube-bridge -j ACCEPT iptables -A FORWARD -i kube-bridge -j ACCEPT
The text was updated successfully, but these errors were encountered:
Add iptable rule in filter table FORWRD chain to allow traffic in and…
8d92d36
… out to the pods Fixes #120
Testing the patch #127 figured that we need one more rule in case service proxy to permit node-port traffic.
iptables -t filter -A FORWARD -o ens33 -j ACCEPT
Sorry, something went wrong.
11a779f
murali-reddy
No branches or pull requests
By default Linux hasfilter
tableFORWARD
chain has default policy asDROP
.Its actually policy by Docker 1.13 moby/moby#28257
Some possible options for CNI plugins kubernetes/kubernetes#40182
I guess Kube-router should add exception atleast to permit the traffic from
kube-bridge
interfaceThe text was updated successfully, but these errors were encountered: