Skip to content

Finalize egress traffic supported for GA #1339

Closed
7 of 7 issues completed
Closed

Description

@haiyanmeng

This issue aims to finalize the egress traffic supported for GA.

Activity

  1. EItanya commented on Sep 1, 2026

    @EItanya
    Collaborator

    I agree we will need this eventually, but we explicitly said at the offsite we would NOT do this for the initial milestone.

  2. self-assigned this
    on Sep 18, 2026
  3. added this to the M3 milestone on Sep 18, 2026
  4. changed the title [-]Egress policies for different network protocols[/-] [+]Finalize egress traffic supported in GA[/+] on Sep 18, 2026
  5. changed the title [-]Finalize egress traffic supported in GA[/-] [+]Finalize egress traffic supported for GA[/+] on Sep 18, 2026
  6. haiyanmeng commented on Sep 28, 2026

    @haiyanmeng
    CollaboratorAuthor

    Eitan Yarmush (@EItanya) , Keith Mattix II (@keithmattix) , Bowei Du (@bowei) , Lior Lieberman (@LiorLieberman) I created #1937 and #1938 to align the two data planes with the supported egress traffic for GA: https://github.com/agent-substrate/substrate/blob/main/docs/egress-traffic.md.

    After closing these two issues, we can add e2e tests to make sure the data planes behave correctly for egress traffic #1787 .

    WDYT?

  7. EItanya commented on Oct 21, 2026

    @EItanya
    Collaborator

    All sub issues are completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area/networkkind/featureAn enhancement / feature request or implementation

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions