migrating from nginx, matching annotations

[davem-git]

going from nginx ingress to envoy gateway HTTPRoute, we have a lot of teams with annotations on the ingress. Is there away to match this setup with envoy gateway?

kind: Ingress
metadata:
    annotations:
        kubernetes.io/ingress.class: nginx
        nginx.ingress.kubernetes.io/configuration-snippet: |
            send_timeout              600s;                     
            proxy_ignore_client_abort on;                       
        nginx.ingress.kubernetes.io/proxy-body-size: 128m       
        nginx.ingress.kubernetes.io/proxy-buffer-size: 16k     
        nginx.ingress.kubernetes.io/proxy-connect-timeout: "50" 
        nginx.ingress.kubernetes.io/proxy-read-timeout: "600"  
        nginx.ingress.kubernetes.io/proxy-send-timeout: "600"  

timeouts i think are replaced with

timeouts:
        request: 600s  # Replaces proxy-send-timeout + configuration-snippet send_timeout
        backendRequest: 600s # Combines proxy-connect-timeout + proxy-read-timeout

can i add headers to support the rest

filters:
        - type: RequestHeaderModifier
          requestHeaderModifier:
            set:
            - name: x-envoy-upstream-rq-timeout-ms
              value: "600000"
            - name: x-envoy-max-request-bytes
              value: "134217728"
            - name: x-envoy-buffer-limit-bytes
              value: "16384"
            - name: x-envoy-upstream-rq-per-try-timeout-ms
              value: "600000"

[arkodg]

Adding the additional ones

1. timeout.tcp.connectTimeout in BTP https://gateway.envoyproxy.io/docs/api/extension_types/#tcptimeout
2. proxy-body-size is being worked on rn api: Add BufferRequests field to BackendTrafficPolicy #5537, should be available in v1.4 (end April)
3. per connection buffer https://gateway.envoyproxy.io/docs/tasks/traffic/client-traffic-policy/#configure-downstream-per-connection-buffer-limit

[davem-git]

the per connection buffer, thats per gateway right? we couldn't have set per httproute?

[arkodg]

thats per downstream connection, for upstream connections there's https://gateway.envoyproxy.io/docs/api/extension_types/#backendconnection which can be set in BTP