-
Notifications
You must be signed in to change notification settings - Fork 3.4k
iptables: Add a fallback to missing xt_socket module. #10299
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
Conversation
In non-tunneled datapath modes a missing xt_socket module breaks proxy redirection traffic. xt_socket is needed due to interaction between kernel's ip early demux logic and an explicit drop for skbs with a socket set in ip_forward(). If xt_socket is not available we can work around this problem by disabling ip early demux. Add a cilium configuration option 'enable-xt-socket-fallback' which is 'true' by default, meaning that cilium-agent is allowed to disable ip early demux if needed. This new option can be set to false to retain the current behavior (== ip early demux is not disabled, but Cilium policy enforcement may not function correctly in all datapath modes with L7 enforcement or visibility. Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
Release note label not set, please set the appropriate release note. |
1 similar comment
Release note label not set, please set the appropriate release note. |
haveIp6tables bool | ||
haveSocketMatch bool | ||
waitArgs []string | ||
haveIp6tables bool |
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.
struct field haveIp6tables should be haveIP6tables
test-me-please |
f3bd304
to
f7dbd53
Compare
test-me-please |
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. Please add a note in the docs as well.
Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
Added docs. |
test-me-please |
k8s could not terminate pods before timing out, retesting. https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/17447/execution/node/178/log/ |
test-me-please |
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.
I have a few suggestions to streamline the docs below.
Issued #10325 to fix the Istio PODs lingering problem now plaguing k8s 1.17. |
82afd97
to
b8a25e9
Compare
test-docs-please |
test-me-please |
test-me-please |
In non-tunneled datapath modes a missing xt_socket module breaks proxy
redirection traffic. xt_socket is needed due to
interaction between kernel's ip early demux logic and an explicit drop
for skbs with a socket set in ip_forward(). If xt_socket is not
available we can work around this problem by disabling ip early demux.
Add a cilium configuration option 'enable-xt-socket-fallback' which is
'true' by default, meaning that cilium-agent is allowed to disable ip
early demux if needed. This new option can be set to false to retain
the current behavior (== ip early demux is not disabled, but Cilium
policy enforcement may not function correctly in all datapath modes
with L7 enforcement or visibility.
Signed-off-by: Jarno Rajahalme jarno@covalent.io
This change is