diff --git a/assets/agw-docs/pages/reference/api/main/agentgateway.dev_agentgatewayparameters.yaml.html b/assets/agw-docs/pages/reference/api/main/agentgateway.dev_agentgatewayparameters.yaml.html
index 21136e1d5..438840e74 100644
--- a/assets/agw-docs/pages/reference/api/main/agentgateway.dev_agentgatewayparameters.yaml.html
+++ b/assets/agw-docs/pages/reference/api/main/agentgateway.dev_agentgatewayparameters.yaml.html
@@ -819,7 +819,7 @@
- name: everything
stdio:
cmd: npx
- args: ["@modelcontextprotocol/server-everything"]Validation
Documentation References (4)
Validation
Documentation References (6)
https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
for details.Documentation References (1)
that are used by this container.
DynamicResourceAllocation feature gate.Validation
the Pod where this field is used. It makes that resource available
inside a container.Service. Defaults to ServiceValidation
Documentation References (1)
Validation
Documentation References (1)
ServiceValidation
Documentation References (1)
Gateway. Listener andListenerSet are not valid targets.
merge. For example, policy A sets tcp and tls, and policy B setstls; the effective policy would be tcp from policy A, and tls from
policy B.Validation
Documentation References (20)
Gateway. Listener andListenerSet are not valid targets.
merge. For example, policy A sets tcp and tls, and policy B setstls; the effective policy would be tcp from policy A, and tls from
policy B.Validation
Documentation References (22)
Documentation References (7)
logged.Validation
The value is a CEL expression. If the CEL expression fails to evaluate,
the pair will be excluded.Validation
When unset, legacy human-oriented fields are used.Otel selects the OTel-aligned built-in HTTP field set.Validation
Documentation References (1)
Validation
Validation
Validation
This only applies to HTTP/1. If a request is HTTP/2 in either the incoming or outgoing request, this will be ignored.
HTTP/2 requests are always lower case.Validation
closed.
If unset, this defaults to 10 minutes.Validation
Documentation References (1)
in HTTP/1.1 requests.
If unset, this defaults to 100.Validation
Documentation References (1)
request headers.
If unset, this defaults to 16Ki.Validation
control for received data.Validation
Documentation References (1)
into memory.
Bodies will only be buffered for policies which require buffering.
If unset, this defaults to 2mb.Validation
Documentation References (1)
This includes HTTP/1 requests and HTTP/2 streams. Requests over the limit
are rejected immediately with a 503 response. Unset means unlimited.Validation
This includes HTTP/1 requests and HTTP/2 streams. Requests over the limit
are rejected immediately with a 503 response. Unset means unlimited.Validation
Documentation References (1)
After this duration, the connection is gracefully closed after the current in-flight request completes.
Useful for ensuring even traffic distribution behind load balancers during scaling events.Validation
normalize defines path normalization rules applied before route matching.
The normalized path is used for routing, policies and the upstream request;
access logs keep the original path. Rules are applied in a fixed order
regardless of how they are listed: percent-decoding, then MergeSlash,
then DotSegment.%00 are rejected with 400 whenever any rule
other than MergeSlash is set.MergeSlash collapses repeated slashes into one, treating \ as /.DotSegment resolves . and .. segments, treating %2E as ., \ as /,
and ignoring parameters on dot segments (..;x).DecodeUnreserved decodes percent-encoded unreserved characters (A-Z a-z 0-9 - . _ ~).RejectEscapedSlash rejects requests whose path contains %2F or %5C with 400.UnescapeSlash decodes %2F and %5C into /.Validation
normalize defines path normalization rules applied before route matching.
The normalized path is used for routing, policies and the upstream request;
access logs keep the original path. Rules are applied in a fixed order
regardless of how they are listed: percent-decoding, then MergeSlash,
then DotSegment.%00 are rejected with 400 whenever any rule
other than MergeSlash is set.MergeSlash collapses repeated slashes into one, treating \ as /.DotSegment resolves . and .. segments, treating %2E as ., \ as /,
and ignoring parameters on dot segments (..;x).DecodeUnreserved decodes percent-encoded unreserved characters (A-Z a-z 0-9 - . _ ~).RejectEscapedSlash rejects requests whose path contains %2F or %5C with 400.UnescapeSlash decodes %2F and %5C into /.Validation
Documentation References (2)
CEL expressions are evaluated per-request and added as labels to all
Prometheus metrics exposed by agentgateway.Documentation References (1)
added to Prometheus metrics.Validation
Documentation References (1)
to all Prometheus metrics. The value is a CEL expression evaluated
per-request. If the CEL expression fails to evaluate, the label value
is set to "unknown".
increase Prometheus storage and memory usage. Prefer low-cardinality
dimensions like team or environment.Validation
Documentation References (1)
normal protocol handling. This can also be configured to allow both
PROXY and non-PROXY traffic on the same listener.Strict.Validation
V2.Validation
Validation
Documentation References (1)
Validation
Documentation References (2)
Documentation References (1)
If unset, this defaults to 180s.Validation
Documentation References (1)
If unset, this defaults to 9.Validation
Documentation References (1)
If unset, this defaults to 180s.Validation
Documentation References (1)
Connections over the limit are closed immediately. Unset means unlimited.Validation
Connections over the limit are closed immediately. Unset means unlimited.Validation
Documentation References (1)
Validation
Documentation References (1)
ALPN)
value to use in the TLS handshake.["h2", "http/1.1"].Validation
Documentation References (1)
The value is a comma-separated list of cipher suites, for exampleTLS13_AES_256_GCM_SHA384,TLS13_AES_128_GCM_SHA256.
Use this in the TLS options field of a TLS listener.Documentation References (1)
At most one of sectionName or port may be set.
Only valid on frontend policies targeting a Gateway.Validation
Validation
Gateway (optionally, with asectionName indicating the listener), ListenerSet, or Route
(optionally, with a sectionName indicating the route rule).
merge. Precedence is given to more precise policies: Gateway <Listener < Route < Route Rule. For example, policy A setstimeouts and retries, and policy B sets retries; the effective
policy would be timeouts from policy A, and retries from policy B.Validation
Documentation References (61)
Gateway (optionally, with asectionName indicating the listener), ListenerSet, or Route
(optionally, with a sectionName indicating the route rule).
merge. Precedence is given to more precise policies: Gateway <Listener < Route < Route Rule. For example, policy A setstimeouts and retries, and policy B sets retries; the effective
policy would be timeouts from policy A, and retries from policy B.Validation
Documentation References (62)
key.Validation
Documentation References (2)
ConfigMap resources
containing API keys. It is ConfigMap-only; use secretRef orsecretSelector for Secret-backed credentials. If the same key is
defined in multiple ConfigMaps, the behavior is undefined.
ConfigMap must use keyHash; a raw key value is rejected.ConfigMap data represents one API key. The key is
an arbitrary identifier. The value must be a JSON object withkeyHash, plus optional metadata. keyHash contains a hashed API
key in sha256:<hex> format. metadata contains arbitrary JSON
metadata associated with the key, which may be used by other
policies. For example, you may write an authorization policy allowingapiKey.group == 'sales'.apiVersion: v1
kind: ConfigMap
@@ -2579,10 +2579,10 @@
}
client2: "k-456"Documentation References (1)
Documentation References (1)
permissions.
If multiple authorization rules are applied across different policies, at the same or different attachment points,
all rules are merged.Documentation References (11)
If unspecified, defaults to Allow.Require rules are cumulative: all require rules must match.Validation
Documentation References (11)
Allow: any matching allow rule allows the request.
* Require: every require rule must match for the request to be allowed.
* Deny: any matching deny rule denies the request.Deny is not recommended because expression failures fail to deny; preferAllow or Require. If used, design expressions defensively against evaluation errors.Allow rule is configured, requests are denied unless at
least one allow rule matches.Documentation References (11)
action. For Allow and Deny, any single matching expression
applies the action; for Require, every expression must match.Validation
Documentation References (11)
permissions.
If multiple authorization rules are applied across different policies, at the same or different attachment points,
all rules are merged.Documentation References (12)
If unspecified, defaults to Allow.Require rules are cumulative: all require rules must match.Validation
Documentation References (12)
Allow: any matching allow rule allows the request.
* Require: every require rule must match for the request to be allowed.
* Deny: any matching deny rule denies the request.Deny is not recommended because expression failures fail to deny; preferAllow or Require. If used, design expressions defensively against evaluation errors.Allow rule is configured, requests are denied unless at
least one allow rule matches.Documentation References (12)
action. For Allow and Deny, any single matching expression
applies the action; for Require, every expression must match.Validation
Documentation References (12)
Basic
authentication scheme (RFC 7617), where a username and password are
encoded in the request.Validation
Documentation References (1)
If omitted, credentials are read from the Authorization header with the Basic prefix.Validation
Strict.Validation