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
Allow setting TCP MSS clamping value also for non GN #2087
Conversation
|
🤖 Created branch: z_pr2087/yboaron/clamp_non_gn |
| @@ -62,7 +62,7 @@ var logger = log.Logger{Logger: logf.Log.WithName("MTU")} | |||
|
|
|||
| func NewMTUHandler(localClusterCidr []string, isGlobalnet bool, tcpMssValue int) event.Handler { | |||
| forceMss := notNeeded | |||
| if isGlobalnet { | |||
| if isGlobalnet || tcpMssValue != 0 { | |||
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.
Not in the scope of this PR, but we should probably add some validation on the MTU value that is configured by the user (i.e., to ensure that its in the valid reasonable range)
|
This would need a backport to both |
We noticed in some cases MTU issues even when GN was disabled. This PR allows the user to force a particular MSS clamping value also for non GN. To force a particular MSS clamping value use the submariner.io/tcp-clamp-mss node annotation on Gateway nodes. e.g. kubectl annotate node <node_name> submariner.io/tcp-clamp-mss=<value> Signed-off-by: Yossi Boaron <yboaron@redhat.com>
fceea87
to
1186509
Compare
|
🤖 Closed branches: [z_pr2087/yboaron/clamp_non_gn] |
) We noticed in some cases MTU issues even when GN was disabled. This PR allows the user to force a particular MSS clamping value also for non GN. To force a particular MSS clamping value use the submariner.io/tcp-clamp-mss node annotation on Gateway nodes. e.g. kubectl annotate node <node_name> submariner.io/tcp-clamp-mss=<value> Signed-off-by: Yossi Boaron <yboaron@redhat.com> (cherry picked from commit 9e47bd0)
) We noticed in some cases MTU issues even when GN was disabled. This PR allows the user to force a particular MSS clamping value also for non GN. To force a particular MSS clamping value use the submariner.io/tcp-clamp-mss node annotation on Gateway nodes. e.g. kubectl annotate node <node_name> submariner.io/tcp-clamp-mss=<value> Signed-off-by: Yossi Boaron <yboaron@redhat.com> (cherry picked from commit 9e47bd0)
We noticed in some cases MTU issues even when GN was disabled. This PR allows the user to force a particular MSS clamping value also for non GN. To force a particular MSS clamping value use the submariner.io/tcp-clamp-mss node annotation on Gateway nodes. e.g. kubectl annotate node <node_name> submariner.io/tcp-clamp-mss=<value> Signed-off-by: Yossi Boaron <yboaron@redhat.com> (cherry picked from commit 9e47bd0)
We noticed in some cases MTU issues even when GN was disabled. This PR allows the user to force a particular MSS clamping value also for non GN. To force a particular MSS clamping value use the submariner.io/tcp-clamp-mss node annotation on Gateway nodes. e.g. kubectl annotate node <node_name> submariner.io/tcp-clamp-mss=<value> Signed-off-by: Yossi Boaron <yboaron@redhat.com> (cherry picked from commit 9e47bd0)
Signed-off-by: Yossi Boaron <yboaron@redhat.com>
Signed-off-by: Yossi Boaron <yboaron@redhat.com>
We noticed in some cases MTU issues even when
GN was disabled.
This PR allows the user to force a particular MSS clamping value
also for non GN.
To force a particular MSS clamping value use the submariner.io/tcp-clamp-mss
node annotation on Gateway nodes.
e.g. kubectl annotate node <node_name> submariner.io/tcp-clamp-mss=<value>
Signed-off-by: Yossi Boaron yboaron@redhat.com