[Automated] Draft docs (agentgateway): gateway api: support new backend url rewrite filter

[github-actions]

agentgateway/agentgateway#3755 — gateway api: support new backend url rewrite filter

Docs versions: standalone/main, kubernetes/main

What changes for users: Kubernetes HTTPRoute backendRefs can now carry a URLRewrite filter in spec.rules.backendRefs.filters, so a host or path rewrite can apply only to the selected backendRef instead of the whole route rule.

What the docs now say: The Host rewrites and Path rewrites guides now show backend-specific rewrite sections with the spec.rules.backendRefs.filters.urlRewrite shape for host and path rewrites.

Not verified: No cluster was configured for this run, so the examples are unrun.

How agentgateway-3755 was drafted, and what was not verified

• Code PR: gateway api: support new backend url rewrite filter agentgateway#3755
• Code issue: none linked
• Product: agentgateway (upstream) → agentgateway/website
• Docs version: standalone/main and kubernetes/main. The change is documented in the development tree, which is where unreleased changes go.
• Category: scoped-edit / pr

Plan, and what changed it

• Planned: Add backendRef URLRewrite coverage to the Kubernetes rewrite guides, and check the broad standalone urlRewrite hit.
• Learned: the code diff adds HTTPRouteFilterURLRewrite handling in BuildAgwBackendPolicyFilters; the standalone rewrites page already covers route-level policies.urlRewrite and no standalone schema field changed.
• Did: Added gated Kubernetes-only backend-specific sections to the host and path rewrite guides.

Why a documentation change is necessary

The existing rewrite guides show URLRewrite under spec.rules.filters, which applies the rewrite to the whole HTTPRoute rule. The pull request adds support for the same Gateway API URLRewrite filter under backendRefs[].filters, where the rewrite applies only to the selected backend. Without an update, a reader cannot discover the backend-specific field path from the task guides. The other target pages that mention URLRewrite use rule-level filters or example output that remains accurate.

What changed on disk

• assets/agw-docs/pages/traffic-management/rewrite/host.md: Added a main-only Kubernetes section that shows spec.rules.backendRefs.filters.urlRewrite.hostname.
• assets/agw-docs/pages/traffic-management/rewrite/path.md: Added a main-only Kubernetes section that shows spec.rules.backendRefs.filters.urlRewrite.path.

How to verify this change

1. Apply an HTTPRoute like the new backend-specific path rewrite example, with type: URLRewrite under spec.rules[0].backendRefs[0].filters.
2. Run kubectl get httproute backend-path-rewrite -n httpbin -o jsonpath="{.status.parents[0].conditions[?(@.type=='Accepted')].status}" and expect True.
3. Send a request to /headers on the route hostname and expect the upstream response URL to contain /anything.

Proposed release note

No proposed release note: the planner listed both standalone/main and kubernetes/main, but the diff and documentation change are Kubernetes-only. A generated note from this item would be placed on the standalone release notes too.

What was not verified

The configuration was not applied to a cluster.

The new HTTPRoute examples are unrun.

How the pages were chosen (triage report)

Draft a documentation change

agentgateway/agentgateway#3755 — gateway api: support new backend url rewrite filter

• Product: agentgateway (upstream) → agentgateway/website
• Docs version: standalone/main, kubernetes/main
• Summary (read from the body): gateway api: support new backend url rewrite filter
• Not tested: no cluster was available, so every command in this diff is unrun
• No rule covers 2 touched file(s). The candidate pages below come from the files that DID match a rule, so they may scope this narrower than the change is. Read these before deciding the change is only about the pages listed:
  • api/resource.pb.go
  • crates/agentgateway/src/proxy/httpproxy.rs

Draft branch: pr-tracker-draft-agentgateway-3755

[cloudflare-workers-and-pages]

Deploying agentproxy with    Cloudflare Pages

Latest commit:	e07042a
Status:	✅  Deploy successful!
Preview URL:	https://0a3dd5a4.agentproxy.pages.dev
Branch Preview URL:	https://pr-tracker-draft-agentgatewa-xvpq.agentproxy.pages.dev

View logs