Skip to content

Document the egress traffic supported for GA - #1749

Merged
Bowei Du (bowei) merged 1 commit into
agent-substrate:mainfrom
haiyanmeng:egress-supported-traffic-ga
Sep 21, 2026
Merged

Bowei Du (bowei) merged 1 commit into
agent-substrate:mainfrom
haiyanmeng:egress-supported-traffic-ga

Conversation

@haiyanmeng

@haiyanmeng haiyanmeng commented Sep 18, 2026

Copy link
Copy Markdown
Collaborator

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

It's a good idea to open an issue first for discussion.

  • Tests pass
  • Appropriate changes to documentation are included in the PR

Comment thread docs/egress-traffic.md Outdated
Comment thread docs/egress-traffic.md
Comment thread docs/egress-traffic.md Outdated
Comment thread docs/egress-traffic.md Outdated
@haiyanmeng
haiyanmeng force-pushed the egress-supported-traffic-ga branch from 426b52f to 90e534e Compare September 18, 2026 21:51
Comment thread docs/egress-traffic.md
Comment thread docs/egress-traffic.md
Comment thread docs/egress-traffic.md
Comment thread docs/egress-traffic.md
Comment thread docs/egress-traffic.md

@bowei Bowei Du (bowei) left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't have to be perfect and we can update this to match what is implemented for mega atelet when that lands

@haiyanmeng
haiyanmeng force-pushed the egress-supported-traffic-ga branch from 90e534e to 0b7a4c2 Compare September 21, 2026 17:28
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.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks about right; we can always iterate

@bowei
Bowei Du (bowei) added this pull request to the merge queue Sep 21, 2026
Merged via the queue into agent-substrate:main with commit dc1f263 Sep 21, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/network kind/docs Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants