Conversation
Signed-off-by: Art Berger <[email protected]>
artberger
added
documentation
Deploying agentproxy with
|
| Latest commit: |
fdfc915
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7dd8366b.agentproxy.pages.dev |
| Branch Preview URL: | https://adb-policy-info.agentproxy.pages.dev |
|
|
||
| Agentgateway processes each request through four phases in the following order. You cannot change the phase order, but you can control which filters run in each phase by configuring the appropriate policy sections. | ||
|
|
||
| ```mermaid |
There was a problem hiding this comment.
looks like this:
| description: Learn about how AgentgatewayPolicy sections target different Kubernetes resource types, and how policies are merged when multiple policies apply to the same resource. | ||
| --- | ||
|
|
||
| {{< reuse "agw-docs/pages/agentgateway/about/policies.md" >}} |
There was a problem hiding this comment.
not sure we needed it in 2.2.x as pre/ post routing was not in place
| | 11 | Cross-Site Request Forgery (CSRF) | `csrf` | | ||
| | 12 | Header modifiers | `headerModifiers` | | ||
| | 13 | Host rewrite | `hostRewrite` | | ||
| | 14 | Direct response | `directResponse` | |
There was a problem hiding this comment.
I am assuming this is only supported in the postrouting phase since not all of these are supported in the prerouting phase?
| | 13 | Host rewrite | `hostRewrite` | | ||
| | 14 | Direct response | `directResponse` | | ||
|
|
||
| ### PreRouting filters |
There was a problem hiding this comment.
| ### PreRouting filters | |
| ### Supported PreRouting filters |
| | -- | -- | -- | -- | | ||
| | `frontend` | Gateway | Not allowed | Applies to all listeners on the targeted Gateway. | | ||
| | `traffic` | Gateway, HTTPRoute, GRPCRoute, ListenerSet | Optional | When targeting a Gateway, the `sectionName` selects a specific listener. When targeting an HTTPRoute or GRPCRoute, the `sectionName` selects a specific route rule. | | ||
| | `backend` | Gateway, HTTPRoute, GRPCRoute, ListenerSet, Service, {{< reuse "agw-docs/snippets/agentgateway/agentgatewaybackend.md" >}} | Optional | When targeting a Service, the `sectionName` selects a specific port. When targeting an {{< reuse "agw-docs/snippets/agentgateway/agentgatewaybackend.md" >}}, the `sectionName` selects a specific sub-backend. | |
There was a problem hiding this comment.
is gateway really supported as a backend?
There was a problem hiding this comment.
Yes! For example, you may want to do "for all calls to all backends enable keepalives" etc.
| | -- | -- | | ||
| | `frontend` | Field-level merge across policies that target the same Gateway. | | ||
| | `traffic` | Gateway < Listener < Route < Route Rule | | ||
| | `backend` | Gateway < Listener < Route < Route Rule < Backend/Service | |
There was a problem hiding this comment.
This is a bit off. While AgentgatewayPolicy can currently on targetRef things, there is inline filters in HTTPRoute which translate down to the same policy concept in the data plane. i nthe future we may allow filters pointing to AGWPolicy as well.
Gateway < Listener < Route (targetRef) < Route Rule (targetRef) < Backend (targetRef) < backend (inline on backend object) < route backend ref (inline on route )
3 participants
Closes #336