Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update document antrea-proxy.md #6274

Merged
merged 1 commit into from
May 8, 2024
Merged

Update document antrea-proxy.md #6274

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions docs/antrea-proxy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -253,6 +253,26 @@ data:
proxyLoadBalancerIPs: false
```

With the above configuration, AntreaProxy will ignore all external `loadBalancerIP`s.
Copy link
Contributor

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.?

Copy link
Contributor Author

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.

Copy link
Contributor

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 loadBalancerIPs and LoadBalancerIPs

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Starting with K8s v1.29, feature [LoadBalancerIPMode](https://kubernetes.io/docs/concepts/services-networking/service/#load-balancer-ip-mode)
was introduced, providing users with a more fine-grained mechanism to control how
every external `loadBalancerIP` behaves in a LoadBalancer Service.

- If the value of `LoadBalancerIPMode` is `LoadBalancerIPModeVIP` or nil, the
traffic destined for the corresponding external `loadBalancerIP` should follow
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.

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
`LoadBalancerIPModeProxy` will bypass AntreaProxy. If the configuration option
`proxyLoadBalancerIPs` is set to `false`, AntreaProxy will ignore the external
`loadBalancerIP`s even if configured with `LoadBalancerIPModeVIP`.

There are two important prerequisites for this feature:

* You must enable `proxyAll` and [remove kube-proxy](#removing-kube-proxy) from
Expand Down