-
Notifications
You must be signed in to change notification settings - Fork 370
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
Document LoadBalancerMode related feature gate and configuration #5251
Conversation
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.
minor comments and suggestions, otherwise lgtm
docs/antrea-proxy.md
Outdated
Nodes. Currently, it has two options: nat (default) and dsr. | ||
|
||
* In NAT mode, external traffic is SNAT'd when it's load balanced across Nodes | ||
to ensure symmetric path. It's the default and the most applicable mode. |
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.
to ensure symmetric path. It's the default and the most applicable mode. | |
to ensure symmetric paths. It's the default and the most general mode. |
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.
done
docs/antrea-proxy.md
Outdated
* In DSR mode, external traffic is never SNAT'd and backend Pods running on | ||
Nodes that are not the ingress Node can reply to clients directly, bypassing | ||
the ingress Node. Therefore, traffic in DSR mode usually has lower latency, | ||
higher output bandwidth, and preserved client IP. Currently, it is applicable |
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.
higher output bandwidth, and preserved client IP. Currently, it is applicable | |
higher throughput, and can preserve client IP. Currently, it is only applicable |
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.
done
docs/antrea-proxy.md
Outdated
Nodes that are not the ingress Node can reply to clients directly, bypassing | ||
the ingress Node. Therefore, traffic in DSR mode usually has lower latency, | ||
higher output bandwidth, and preserved client IP. Currently, it is applicable | ||
to Linux Nodes, encap mode, and IPv4 cluster. The feature gate |
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.
s/cluster/clusters
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.
done
docs/antrea-proxy.md
Outdated
`LoadBalancerModeDSR` must be enabled to use this mode for any Service. | ||
|
||
You can make the following changes to the `antrea-config` ConfigMap to specify | ||
load balancer mode for all Services: |
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.
a load balancer mode
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.
changed to "the default load balancer mode".
docs/feature-gates.md
Outdated
mode determines how external traffic destined to LoadBalancerIPs and ExternalIPs of Services is processed when it's load | ||
balanced across Nodes. In DSR mode, external traffic is never SNAT'd and backend Pods running on Nodes that are not the | ||
ingress Node can reply to clients directly, bypassing the ingress Node. Therefore, traffic in DSR mode usually has lower | ||
latency, higher output bandwidth, and preserved client IP. It's only meaningful to use feature when AntreaProxy is |
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.
same suggestion as above
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.
done
docs/feature-gates.md
Outdated
|
||
#### Requirements for this Feature | ||
|
||
- `AntreaProxy` is enabled. |
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 feel like there are more requirements, which we typically list here:
AntreaProxy
withproxyAll
is enabled.- IPv4 only
- Linux Nodes only
- Encap mode only
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.
added
docs/antrea-proxy.md
Outdated
can be used to specify how you want AntreaProxy to handle external traffic | ||
destined to LoadBalancerIPs and ExternalIPs of Services. Specifically, the mode | ||
determines how external traffic is processed when it's load balanced across | ||
Nodes. Currently, it has two options: nat (default) and dsr. |
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.
nat
(defualt) and dsr
?
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.
sorry, what do you mean?
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 meant add "`" around "nat" and "drs".
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.
done
021ad52
to
0e3792a
Compare
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.
a couple nits, LGTM
docs/antrea-proxy.md
Outdated
|
||
* In DSR mode, external traffic is never SNAT'd and backend Pods running on | ||
Nodes that are not the ingress Node can reply to clients directly, bypassing | ||
the ingress Node. Therefore, DSR mode can preserve client IP of requests, and |
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.
nit: the client IP
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.
done
docs/antrea-proxy.md
Outdated
@@ -218,3 +274,8 @@ There are two important prerequisites for this feature: | |||
greater than 65535 seconds will be truncated and the Antrea Agent will log a | |||
warning. [We do not intend to address this | |||
limitation](https://github.com/antrea-io/antrea/issues/1578). | |||
* Due to the use of the "learn" action on the implementation of DSR mode, the |
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.
s/on/in
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.
fixed
/skip-all |
Signed-off-by: Quan Tian <[email protected]>
@antoninbas just removed an empty in the latest update. |
/skip-all |
For #5025