-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Drop ephemeral port range check for NodePort from datapath #10782
Conversation
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.
One nit below.
9ece33a
to
a7bdbcb
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.
If we are going to backport this it requires upgrade notes.
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.
With @aanm's feedback applied, the rest looks good, thx.
a7bdbcb
to
f7324ed
Compare
@aanm Updated the upgrade guide. |
test-me-please |
test-docs-please |
f7324ed
to
d2d5426
Compare
test-me-please |
This commit removes the ephemeral port range check for NodePort from the BPF datapath. Instead, in the agent we check whether the NodePort range is covered by ip_local_reserved_ports. If it's not, then we append the range to ip_local_reserved_ports. Users can opt out from the latter by setting --enable-auto-protect-node-port-range=false. Signed-off-by: Martynas Pumputis <[email protected]>
The value configures --enable-auto-protect-node-port-range. The default is true. Signed-off-by: Martynas Pumputis <[email protected]>
Signed-off-by: Martynas Pumputis <[email protected]>
Signed-off-by: Martynas Pumputis <[email protected]>
The 4.19 CI build hit #10821 |
This PR:
net.ipv4.ip_local_reserved_ports
. Modifies it if overlap with the ephemeral range is detected.--enable-auto-protect-node-port-range
(global.nodePort.autoProtectPortRange
in helm) flag do disable the behavior ^^.Reviewable per commit.
Fix #10261.