Skip to content

POC: pluggable ingress for substrate#393

Draft
Jet Chiang (supreme-gg-gg) wants to merge 1 commit into
agent-substrate:mainfrom
supreme-gg-gg:poc/pluggable-ingress
Draft

POC: pluggable ingress for substrate#393
Jet Chiang (supreme-gg-gg) wants to merge 1 commit into
agent-substrate:mainfrom
supreme-gg-gg:poc/pluggable-ingress

Conversation

@supreme-gg-gg

Copy link
Copy Markdown
Contributor

POC for #326, based on the design in https://docs.google.com/document/d/1djurA9d7f7UIW2DhSqyX85Ad8JgkpPPyCbpDy7G7HOs/edit?tab=t.r12pfwjkq9tf#heading=h.68j4yb47rvbt

Key Changes

  • Removed bundled Envoy/xDS proxy from atenet-router, which now only runs actor-aware routing core + ExtProc server
  • manifests/ate-install/atenet-router.yaml is the single (extproc-only) router manifest
  • Examples and docs for deploying Envoy and Agentgatweay using standalone or Gateway API configuration
  • hack/install-ate.sh deploys the basic reference Envoy gateway alongside the router by default, tests are updated
  • DNS controller's default ingress target flipped from atenet-router to atenet-gateway (router no longer serves HTTP)

Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>

agentgateway

Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>

extproc docs

Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>

revised: docs and manifests

Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>

revised: docs and manifests

Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>

remove default envoy and scripts

Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>

cleanup a bit

Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>

cleanup old files from main

Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>
@@ -0,0 +1,84 @@
// Copyright 2026 Google LLC

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.

Is there a reason why some of the files were renamed? I'm not against refactoring, but if you can keep the meaningful changes to a minimal set. If we rename files, ideally you would contain that in its own commit.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I don't think they were renamed, at least not literally. The motivation here is to move from Envoy specific type (which was in errors.go) to a protocol neutral interface in route.go, route_resolve.go, route_errors.go, and that's why some old files are replaced by new ones. If there's any ways to simplify the refactor that you would suggest I'm glad to do that

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.

2 participants