Skip to content

Commit

Permalink
Update the Egress - IPVS interoperability issue in documents (#3896)
Browse files Browse the repository at this point in the history 
The issue was fixed in Antrea v1.7.0. Update the Egress and Service
Load-balancing documents for that.

Signed-off-by: Jianjun Shen <[email protected]>
  • Loading branch information
@jianjuns
jianjuns authored Jun 14, 2022
1 parent 56e9e4a commit 2e35c5f
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 8 deletions.
11 changes: 5 additions & 6 deletions docs/egress.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -298,10 +298,9 @@ This feature is currently only supported for Nodes running Linux and "encap"
mode. The support for Windows and other traffic modes will be added in the
future.

The current implementation of Antrea Egress does not work with the `strictARP`
configuration of `kube-proxy` IPVS mode. The `strictARP` configuration is
required by some Service load balancing solutions including: [Antrea Service
external IP management, MetalLB](service-loadbalancer.md#interoperability-with-kube-proxy-ipvs-mode),
The previous implementation of Antrea Egress before Antrea v1.7.0 does not work
with the `strictARP` configuration of `kube-proxy` IPVS mode. The `strictARP`
configuration is required by some Service load balancing solutions including:
[Antrea Service external IP management, MetalLB](service-loadbalancer.md#interoperability-with-kube-proxy-ipvs-mode),
and kube-vip. It means Antrea Egress cannot work together with these solutions
in a cluster using `kube-proxy` IPVS. We assume this issue will be fixed in a
near future Antrea version.
in a cluster using `kube-proxy` IPVS. The issue was fixed in Antrea v1.7.0.
5 changes: 3 additions & 2 deletions docs/service-loadbalancer.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -350,7 +350,8 @@ $ kubectl describe configmap -n kube-system kube-proxy | grep strictARP
### Issue with Antrea Egress
The current implementation of Antrea Egress does not work with the `strictARP`
If you are using Antrea v1.7.0 or later, please ignore the issue. The previous
implementation of Antrea Egress before v1.7.0 does not work with the `strictARP`
configuration of `kube-proxy`. It means Antrea Egress cannot work together with
Service external IP management or MetalLB layer 2 mode, when `kube-proxy` IPVS
is used. We assume this issue will be fixed in a near future Antrea version.
is used. This issue was fixed in Antrea v1.7.0.

0 comments on commit 2e35c5f

Please sign in to comment.