Skip to content

feat(controller): set appProtocol on agent Service when a2aConfig is set#1845

Open
mesutoezdil wants to merge 1 commit into
kagent-dev:mainfrom
mesutoezdil:feat/a2a-service-appprotocol
Open

feat(controller): set appProtocol on agent Service when a2aConfig is set#1845
mesutoezdil wants to merge 1 commit into
kagent-dev:mainfrom
mesutoezdil:feat/a2a-service-appprotocol

Conversation

@mesutoezdil
Copy link
Copy Markdown
Contributor

Closes #1808

When an agent has a2aConfig set, the operator-managed Service port now gets appProtocol: kgateway.dev/a2a. This lets agentgateway detect and handle A2A traffic automatically, without the user having to create a separate wrapper Service per agent.

Without this change, the agent card URL rewriting that agentgateway does for A2A does not work, because the proxy sees the traffic as plain HTTP. The only workaround today is a manually maintained sibling Service for each A2A agent.

Agents without a2aConfig are not affected.

Copilot AI review requested due to automatic review settings May 11, 2026 18:50
@github-actions github-actions Bot added the enhancement New feature or request label May 11, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

When an agent has a2aConfig, the generated Service port now carries
appProtocol: kgateway.dev/a2a so agentgateway can detect and route
A2A traffic without manual wrapper Services.

Signed-off-by: mesutoezdil <mesudozdil@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE] Set appProtocol: kgateway.dev/a2a on agent Service when a2aConfig is set

2 participants