The jsonPath configuration for max_request_bytes is invalid.

*Description*:
>What issue is being seen? Describe what should be happening instead of
the bug, for exampleapiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyPatchPolicy
metadata:
labels:
app.kubernetes.io/component: aibrix-gateway-plugin
app.kubernetes.io/managed-by: kubectl
app.kubernetes.io/name: aibrix
app.kubernetes.io/version: nightly
name: aibrix-epp
namespace: aibrix-system
spec:
jsonPatches:
- name: add-buffer-filter
operation:
op: add
path: /http_filters/-
value:
name: envoy.filters.http.router
typed_config:
"@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
max_request_bytes: 52428800 # 50MB（50*1024*1024字节）
type: type.googleapis.com/envoy.config.listener.v3.Listener
- name: aibrix-system/aibrix-eg/http
operation:
op: add
path: /virtual_hosts/0/routes/0
value:
match:
headers:
- name: routing-strategy
string_match:
safe_regex:
regex: .*
prefix: /
name: original_route
route:
cluster: original_destination_cluster
timeout: 120s
typed_per_filter_config:
envoy.filters.http.ext_proc/envoyextensionpolicy/aibrix-system/aibrix-gateway-plugins-extension-policy/extproc/0:
'@type': type.googleapis.com/envoy.config.route.v3.FilterConfig
config: {}
type: type.googleapis.com/envoy.config.route.v3.RouteConfiguration
- name: envoy-patch-policy-override2
operation:
op: add
path: ""
value:
connect_timeout: 6s
dns_lookup_family: V4_ONLY
lb_policy: CLUSTER_PROVIDED
name: original_destination_cluster
original_dst_lb_config:
http_header_name: target-pod
use_http_header: true
type: ORIGINAL_DST
type: type.googleapis.com/envoy.config.cluster.v3.Cluster
- name: increase-max-request-size
operation:
op: add
path: /static_resouce
value: 52428800
type: type.googleapis.com/envoy.config.cluster.v3.Cluster
targetRef:
group: gateway.networking.k8s.io
kind: Gateway
name: aibrix-eg
type: JSONPatch
---
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
labels:
app.kubernetes.io/component: aibrix-gateway-plugin
app.kubernetes.io/managed-by: kubectl
app.kubernetes.io/name: aibrix
app.kubernetes.io/version: nightly
name: aibrix-custom-proxy-config
namespace: aibrix-system
spec:
provider:
kubernetes:
envoyDeployment:
patch:
type: StrategicMerge
value:
spec:
template:
spec:
nodeSelector:
aibrix/deploy: "true" # aibrix 部署标签
containers:
- image: *****/envoyproxy/envoy:v1.33.2
name: envoy
resources:
limits:
cpu: 2
memory: 8Gi
requests:
cpu: 2
memory: 8Gi
- image: ***/envoyproxy/gateway:v1.2.8
name: shutdown-manager
pod:
affinity:
nodeAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- preference:
matchExpressions:
- key: nvidia.com/gpu.present
operator: NotIn
values:
- "true"
weight: 100
podAntiAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- podAffinityTerm:
labelSelector:
matchExpressions:
- key: app.kubernetes.io/name
operator: In
values:
- envoy
topologyKey: kubernetes.io/hostname
weight: 100
replicas: 1
strategy:
rollingUpdate:
maxSurge: 1
maxUnavailable: 1
type: RollingUpdate
envoyPDB:
minAvailable: 1
type: Kubernetes
---

Among them, jsonPatches was invalid:

- name: add-buffer-filter
operation:
op: add
path: /http_filters/-
value:
name: envoy.filters.http.router
typed_config:
"@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
max_request_bytes: 52428800 # 50MB (50*1024*1024 bytes)

execute 5M request parameters:
curl -X POST [http://100.70.147.32:80/v1/chat/completions](http://100.70.147.32/v1/chat/completions) -H "Content-Type: application/json" -H "routing-strategy: prefix-cache-preble" -d @/media/5m.txt

response: Payload Too Large,

how to solve it ? tks