EAI-7243: forward x-ai-eg-backend for header-less metric attribution - #795
Merged
johnl-amd merged 1 commit intoAug 4, 2026
Merged
Conversation
Add x-ai-eg-backend to the default-deny SP's headersToBackend so the resolved backend that discovery forwards (core #4309) reaches the ext_proc and populates aim_service_id on the header-less path, where the gateway can't resolve the backend from EDS endpoint metadata. Stacked on the bump branch (that's where the default-deny SP lives); retarget to main after #794 merges.
johnl-amd
force-pushed
the
prototype-forward-backend-sp
branch
from
August 4, 2026 09:23
23c611e to
be59cff
Compare
johnl-amd
changed the title
johnl-amd
marked this pull request as ready for review
August 4, 2026 09:23
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
1 participant
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.
Summary
x-ai-eg-backendto the default-deny SecurityPolicy'sheadersToBackend.aim_service_idon the header-less/body path — the label went empty when cluster-auth was removed (the gateway can't resolve the backend from EDS endpoint metadata for InferencePool/Service clusters).Merge order
bump_version_envoy_and_ai_gateway(Bump envoy + envoy-ai-gateway; cut ai-gateway over to native API-key auth #794) because the default-deny SP only exists on that branch; base is set to the bump branch for a clean one-line diff.mainafter Bump envoy + envoy-ai-gateway; cut ai-gateway over to native API-key auth #794 merges.Notes
x-ai-eg-backendis on the header path (per-backend SP + native apiKeyAuth) and never hits this extAuth;headersToBackendonly applies to discovery's response on the body path, where discovery is authoritative.Verification (live, app-dev)
Deployed alongside core#4309; header-less traffic (valid key, no routing headers) populated
aim_service_idwith the correct backend — keyed metric series grew on the populated series with no empty-backend series appearing.Risk
Low. Single additive header entry on one gateway-scoped SecurityPolicy.