Document the egress traffic supported for GA - #1749
Merged
Bowei Du (bowei) merged 1 commit intoSep 21, 2026
Merged
Bowei Du (bowei) merged 1 commit into
Bowei Du (bowei) merged 1 commit into
Conversation
haiyanmeng
requested review from
Eitan Yarmush (EItanya),
Lior Lieberman (LiorLieberman),
Bowei Du (bowei) and
Keith Mattix II (keithmattix)
September 18, 2026 19:35
haiyanmeng
commented
Sep 18, 2026
haiyanmeng
force-pushed
the
egress-supported-traffic-ga
branch
from
September 18, 2026 21:51
426b52f to
90e534e
Compare
haiyanmeng
requested review from
Benjamin Elder (BenTheElder) and
Tim Hockin (thockin)
September 18, 2026 22:12
Bowei Du (bowei)
left a comment
Collaborator
There was a problem hiding this comment.
This doesn't have to be perfect and we can update this to match what is implemented for mega atelet when that lands
haiyanmeng
force-pushed
the
egress-supported-traffic-ga
branch
from
September 21, 2026 17:28
90e534e to
0b7a4c2
Compare
Record which egress protocols are allowed, which are allowed only under policy controls, and which are blocked, along with the data path each one takes. Having this written down gives users a single place to check what Substrate lets an actor reach, and gives us a checklist to implement and test against before GA. Point readers at the issue tracker so that requests for traffic we do not yet support arrive with a use case attached.
haiyanmeng
force-pushed
the
egress-supported-traffic-ga
branch
from
September 21, 2026 17:29
0b7a4c2 to
44d8233
Compare
Keith Mattix II (keithmattix)
approved these changes
Sep 21, 2026
Keith Mattix II (keithmattix)
left a comment
Collaborator
There was a problem hiding this comment.
This looks about right; we can always iterate
Bowei Du (bowei)
approved these changes
Sep 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Record which egress protocols are allowed, which are allowed only under policy controls, and which are blocked, along with the data path each one takes. Having this written down gives users a single place to check what Substrate lets an actor reach, and gives us a checklist to implement and test against before GA.
Point readers at the issue tracker so that requests for traffic we do not yet support arrive with a use case attached.
Address #1339