Feature Request: Example of Integration with Envoy Proxy

[rodrigoGA]

Is there an existing issue for this?

• I have searched the existing issues

Describe the problem to be solved

Hello, I’m looking to leverage the Kubernetes Gateway API to integrate the error-pages service with Envoy Proxy as a default backend for HTTP error responses. This feature request would be valuable since Gateway APIs are rapidly gaining adoption.

Suggest a solution

No response

Additional context

No response

[billimek]

@rodrigoGA I got this working in envoy-proxy via something like this using responseOverride:

# BackendTrafficPolicy for backend connection settings - applies to all Gateways
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: BackendTrafficPolicy
metadata:
  name: default
  namespace: kube-system
spec:
  targetSelectors:
    - group: gateway.networking.k8s.io
      kind: Gateway
  compression:
    - type: Zstd
    - type: Brotli
    - type: Gzip
  connection:
    bufferLimit: 16Mi
  tcpKeepalive: {}
  timeout:
    http:
      requestTimeout: 0s
  
  # Custom error page redirects
  responseOverride:    
    # 403 Forbidden
    - match:
        statusCodes:
          - type: Value
            value: 403
      redirect:
        scheme: https
        hostname: error-pages.eviljungle.com
        path:
          type: ReplaceFullPath
          replaceFullPath: /403.html
        statusCode: 302
    
    # 404 Not Found
    - match:
        statusCodes:
          - type: Value
            value: 404
      redirect:
        scheme: https
        hostname: error-pages.eviljungle.com
        path:
          type: ReplaceFullPath
          replaceFullPath: /404.html
        statusCode: 302
    
    # 500 Internal Server Error
    - match:
        statusCodes:
          - type: Value
            value: 500
      redirect:
        scheme: https
        hostname: error-pages.eviljungle.com
        path:
          type: ReplaceFullPath
          replaceFullPath: /500.html
        statusCode: 302
    
    # 502 Bad Gateway
    - match:
        statusCodes:
          - type: Value
            value: 502
      redirect:
        scheme: https
        hostname: error-pages.eviljungle.com
        path:
          type: ReplaceFullPath
          replaceFullPath: /502.html
        statusCode: 302
    
    # 503 Service Unavailable
    - match:
        statusCodes:
          - type: Value
            value: 503
      redirect:
        scheme: https
        hostname: error-pages.eviljungle.com
        path:
          type: ReplaceFullPath
          replaceFullPath: /503.html
        statusCode: 302
    
    # 504 Gateway Timeout
    - match:
        statusCodes:
          - type: Value
            value: 504
      redirect:
        scheme: https
        hostname: error-pages.eviljungle.com
        path:
          type: ReplaceFullPath
          replaceFullPath: /504.html
        statusCode: 302

• error-pages deployment example
• backendtrafficpolicy example