Skip to content

Avoid Istio port collision for actor egress - #1429

Open
hsteude wants to merge 2 commits into
agent-substrate:mainfrom
prokube:fix/ateom-egress-listener-port
Open

Avoid Istio port collision for actor egress#1429
hsteude wants to merge 2 commits into
agent-substrate:mainfrom
prokube:fix/ateom-egress-listener-port

Conversation

@hsteude

@hsteude hsteude commented Sep 3, 2026

Copy link
Copy Markdown

Related to #430. (see discussion)

Summary

Ateom currently uses port 15001 for intercepted Actor egress, which conflicts with Istio's outbound listener.

This changes the default to 16001 for the WorkerPool controller and both Ateom implementations. Port 16001 is not otherwise used by Substrate and does not conflict with Istio's documented ports (i'm happy to change it to somehing else tho). If useful for other integrations, I would also be happy to follow up with a configurable WorkerPool-level port.

Testing

  • make verify

  • Deployed an Istio-injected gVisor WorkerPool

  • Verified Actor ingress, authenticated egress, pause, suspend, and resume

  • Observed no listener conflicts or container restarts

  • Tests pass

  • Appropriate changes to documentation are included in the PR (not
    applicable; this internal default was not previously documented)

"--atunnel-credential-bundle="+atunnelIdentityMountPath+"/credential-bundle.pem",
"--atunnel-trust-bundle="+atunnelIdentityMountPath+"/trust-bundle.pem",
"--atunnel-egress-listen-address=0.0.0.0:15001",
"--atunnel-egress-listen-address=0.0.0.0:16001",

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.

nit: should we keep the ate/8 theme and do 18001?

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.

Seconded

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

How did I miss that chance :D. Made it more at(e)sque.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants