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.

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

Egress Interface remain in down state with externalippool #6310

Open
rajnkamr opened this issue May 9, 2024 · 3 comments
Open

Egress Interface remain in down state with externalippool #6310

rajnkamr opened this issue May 9, 2024 · 3 comments
Labels
kind/documentation Categorizes issue or PR as related to a documentation.

Comments

@rajnkamr
Copy link
Contributor

rajnkamr commented May 9, 2024

Describe the bug

Egress interface shown as down even when ipRanges are in same subnet as Node subnet or otherwise ?
Traffic is going out with actual interface

5: antrea-egress0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
link/ether f2:35:20:81:87:ac brd ff:ff:ff:ff:ff:ff
inet 172.18.0.10/32 scope global antrea-egress0
valid_lft forever preferred_lft forever

To Reproduce

configure extermalippool resource with following config

apiVersion: crd.antrea.io/v1beta1
kind: ExternalIPPool
metadata:
name: external-ip-pool
spec:
ipRanges:

  • start: 172.18.0.10
    end: 172.18.0.20
    nodeSelector: {} # All Nodes can be Egress Nodes

create egress resource under egress crd

apiVersion: crd.antrea.io/v1beta1
kind: Egress
metadata:
name: snat-testapp-ip
spec:
appliedTo:
podSelector:
matchLabels:
app: antrea-test-app ###Select the Pods to which the SNAT Policy will be applied
externalIPPool: external-ip-pool

Expected

Egress interface status should be up

Actual behavior

Versions:

Antrea 2.0/Containerd
Additional context

@rajnkamr rajnkamr added the kind/bug Categorizes issue or PR as related to a bug. label May 9, 2024
@tnqn
Copy link
Member

tnqn commented May 9, 2024

antrea-egress0 is a dummy interface and supposed to be down by design.
The usage of antrea-egress0 is kind of implementation specific. We can add some docs to clarify it but it's not a bug.

@rajnkamr rajnkamr added the kind/documentation Categorizes issue or PR as related to a documentation. label May 9, 2024
@rajnkamr
Copy link
Contributor Author

rajnkamr commented May 9, 2024

@tnqn ,
antrea-egress0 is a dummy interface, however if the externalippool is not in node's subnet, traffic is stopped (expected) and antrea-egress0 remain in down state, however when externalippool is in same subnet as node's network, traffic is going out, however keeping the antrea-egress0 as down might confuse user as src ip will be of antrea-egres0 interface.
Documentation could help to clarify these.

@tnqn tnqn removed the kind/bug Categorizes issue or PR as related to a bug. label May 9, 2024
@rajnkamr
Copy link
Contributor Author

rajnkamr commented May 9, 2024

While using static Egress, when same ip is provided as node's ip, there is no ip assigned to egress dummy interface( antrea-egress0 ), it is expected since ip is already assigned to node's interface, hence can not be reassigned to egress dummy interface
Another candidate for documentation
5: antrea-egress0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
link/ether a2:8d:11:5c:fa:a7 brd ff:ff:ff:ff:ff:ff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to a documentation.
Projects
None yet
Development

No branches or pull requests

2 participants