diff --git a/docs/egress.md b/docs/egress.md index 823f2f0cd07..a003c67b4a8 100644 --- a/docs/egress.md +++ b/docs/egress.md @@ -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. diff --git a/docs/service-loadbalancer.md b/docs/service-loadbalancer.md index b5b1d0958fd..0d2bedd7efa 100644 --- a/docs/service-loadbalancer.md +++ b/docs/service-loadbalancer.md @@ -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.