I have an Ingress
object that I plan to move to Gateway
.
Previously we had an annotation on the Ingress as such:
nginx.ingress.kubernetes.io/proxy-body-size: 100m
What is the equivalent in Istio Gateway?
I have an Ingress
object that I plan to move to Gateway
.
Previously we had an annotation on the Ingress as such:
nginx.ingress.kubernetes.io/proxy-body-size: 100m
What is the equivalent in Istio Gateway?
I have the same question.
I think it’s done via:
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
name: reviews-lua
namespace: bookinfo
spec:
workloadSelector:
labels:
app: reviews
configPatches:
# The first patch adds the lua filter to the listener/http connection manager
- applyTo: HTTP_FILTER
match:
context: SIDECAR_INBOUND
listener:
portNumber: 8080
filterChain:
filter:
name: "envoy.http_connection_manager"
subFilter:
name: "envoy.router"
patch:
operation: INSERT_BEFORE
value: # lua filter specification
name: envoy.lua
config:
inlineCode: |
function envoy_on_request(request_handle)
request_handle:headers():add("request_body_size", request_handle:body():length())
end
On Response:
function envoy_on_response(response_handle)
response_handle:headers():add("response_body_size",
response_handle:body():length())
end
I’m facing 413 payload too large problem on ingressgateway.
Is there any updates on this?
Is that anyone who solved this problem? Using istio 1.11
Where is the proxy-body-size limit specified in the EnvoyFilter config?