HTTP Connection Manager

The HTTP Connection Manager lets you refine the behavior of Envoy for each listener that you manage with Gloo.

Tracing

One of the fields in the HTTP Connection Manager Plugin is tracing. This specifies the listener-specific tracing configuration.

For notes on configuring and using tracing with Gloo, please see the tracing setup docs.

The tracing configuration fields of the Gateway CRD are highlighted below.

apiVersion: gateway.solo.io.v2/v2
kind: Gateway
metadata: # collapsed for brevity
spec:
spec:
  bindAddress: '::'
  bindPort: 8080
  httpGateway:
    plugins:
      httpConnectionManagerSettings:
        tracing:
          verbose: true
          requestHeadersForTags:
            - path
            - origin
status: # collapsed for brevity

Advanced listener configuration

Gloo exposes Envoy’s powerful configuration capabilities with the HTTP Connection Manager. The details of these fields can be found here and here

Below, see a reference configuration specification to demonstrate the structure of the expected yaml.

apiVersion: gateway.solo.io.v2/v2
kind: Gateway
metadata: # collapsed for brevity
spec:
  bindAddress: '::'
  bindPort: 8080
  httpGateway:
    plugins:
      httpConnectionManagerSettings:
        skipXffAppend: false
        via: reference-string
        xffNumTrustedHops: 1234
        useRemoteAddress: false
        generateRequestId: false
        proxy100Continue: false
        streamIdleTimeout: 1m2s
        idleTimeout: 1m2s
        maxRequestHeadersKb: 1234
        requestTimeout: 1m2s
        drainTimeout: 1m2s
        delayedCloseTimeout: 1m2s
        serverName: reference-string
        acceptHttp10: false
        defaultHostForHttp10: reference-string
status: # collapsed for brevity