-
Notifications
You must be signed in to change notification settings - Fork 366
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
Update document antrea-proxy.md #6274
Update document antrea-proxy.md #6274
Conversation
3a6152a
to
5640723
Compare
5640723
to
213eecb
Compare
docs/antrea-proxy.md
Outdated
@@ -253,6 +253,24 @@ data: | |||
proxyLoadBalancerIPs: false | |||
``` | |||
|
|||
It's worth noting that AntreaProxy will bypass all the external `loadBalancerIP`s | |||
with the above configuration. After K8s v1.29, field `LoadBalancerIPMode` was | |||
introduced to `LoadBalancerIngress` in Service status, providing users with a |
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.
What's LoadBalancerIngress
? I don't think it's the name of a field or a feature.
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.
You could find it in this link https://github.com/kubernetes/kubernetes/blob/3f7a50f38688eb332e2a1b013678c6435d539ae6/staging/src/k8s.io/api/core/v1/types.go#L4867. I will rephrase the sentences containing the word LoadBalancerIngress
that confuses readers.
docs/antrea-proxy.md
Outdated
|
||
After Antrea v2.0, AntreaProxy respects `LoadBalancerIPMode` in Service status when | ||
`proxyLoadBalancerIPs` is set to `true`. In this case, AntreaProxy serves only the | ||
external `LoadBalancerIP`s configured with `LoadBalancerIPModeVIP`, bypassing those |
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/bypassing/ignoring
same below
The usage is not correct here IMO, because it is the Service traffic that bypasses AntreaProxy in this case, not AntreaProxy that bypasses the Service traffic.
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.
You are right. The external LoadBalancerIP
s configured with LoadBalancerIPModeProxy
will not be consumed by AntreaProxy, and AntreaProxy never has a chance to bypass them. For those configured with LoadBalancerIPModeVIP
, they are consumed by AntreaProxy, and AntreaProxy can be able to decide to bypass all of them depending on the option proxyLoadBalancerIPs
.
213eecb
to
10151a8
Compare
@@ -253,6 +253,26 @@ data: | |||
proxyLoadBalancerIPs: false | |||
``` | |||
|
|||
With the above configuration, AntreaProxy will ignore all external `loadBalancerIP`s. |
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 suppose it should be loadBalancerIPs
.?
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.
This is used to be consistent with others in this document. See L240.
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 think the current version is fine, but you have to be consistent between loadBalancerIP
s and LoadBalancerIP
s
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
the default behavior and get load-balanced at the source Node. | ||
- If the value of `LoadBalancerIPMode` is `LoadBalancerIPModeProxy`, the traffic | ||
destined for the corresponding external `LoadBalancerIP` should be sent to the | ||
external loadBalancer. |
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.
external loadBalancer. | |
external load balancer. |
or LoadBalancer?
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.
Good catch! It should be external LoadBalancer
.
docs/antrea-proxy.md
Outdated
|
||
Starting with Antrea v2.0, AntreaProxy will respect `LoadBalancerIPMode` in LoadBalancer | ||
Services when the configuration option `proxyLoadBalancerIPs` is set to `true` | ||
(default). In this case, AntreaProxy will serve only the external `LoadBalancerIP`s |
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.
ditto, is LoadBalancerIPs
or loadBalancerIPs
? keep them consistent.
docs/antrea-proxy.md
Outdated
(default). In this case, AntreaProxy will serve only the external `LoadBalancerIP`s | ||
configured with `LoadBalancerIPModeVIP`, as those configured with `LoadBalancerIPMode` | ||
bypass AntreaProxy. If the configuration option `proxyLoadBalancerIPs` is set to | ||
`false`, AntreaProxy will ignore the external `LoadBalancerIP`s even if configured with |
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.
ditto
10151a8
to
da90816
Compare
@@ -253,6 +253,26 @@ data: | |||
proxyLoadBalancerIPs: false | |||
``` | |||
|
|||
With the above configuration, AntreaProxy will ignore all external `loadBalancerIP`s. |
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 think the current version is fine, but you have to be consistent between loadBalancerIP
s and LoadBalancerIP
s
da90816
to
8c9a9a9
Compare
docs/antrea-proxy.md
Outdated
Starting with Antrea v2.0, AntreaProxy will respect `LoadBalancerIPMode` in LoadBalancer | ||
Services when the configuration option `proxyLoadBalancerIPs` is set to `true` | ||
(default). In this case, AntreaProxy will serve only the external `loadBalancerIP`s | ||
configured with `LoadBalancerIPModeVIP` and those configured with |
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.
configured with `LoadBalancerIPModeVIP` and those configured with | |
configured with `LoadBalancerIPModeVIP`, and those configured with |
You need to keep the comma, otherwise the sentence reads a bit differently
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.
My bad, I should notice that your review comment #6274 (comment) doesn't include the comma.
Signed-off-by: Hongliang Liu <lhongliang@vmware.com>
8c9a9a9
to
7bb8bc2
Compare
/skip-all |
@hongliangl please backport to release-2.0 |
In particular, we document how it interacts with the Antrea-specific configuration parameter `proxyLoadBalancerIPs`. Fixes antrea-io#6263 Signed-off-by: Hongliang Liu <lhongliang@vmware.com>
Resolve #6263