HTTP protocol selection

The automatic HTTP/1.1 and HTTP/2 protocol negotiation for Envoy is enabled in Airlock Microgateway by default allowing a wide range of applications to work correctly without further configuration.
However, if you encounter protocol-based problems, you can configure the dedicated HTTP protocol version in the CR SidecarGateway.

 
Functional limitation

Note that with an explicit HTTP protocol version, non-matching requests will be blocked.

Example with HTTP/2-only configuration

In the following example, the downstream and upstream protocol has been set to http2 to ensure that only the HTTP/2 protocol is used by Envoy, e.g., for gRPC-controlled apps.

Example SidecarGateway:

 
Example
apiVersion: microgateway.airlock.com/v1alpha1 
kind: SidecarGateway 
metadata: 
  name: sidecar-gateway-example 
spec: 
  podSelector: 
    matchLabels: 
      app: gRPC-controlled-app 
  applications: 
    - containerPort: 8080 
      downstream:
        protocol: 
          http2: {}   
       routes: 
        - pathPrefix: / 
          secured: {} 
      upstream: 
        protocol: 
          http2: {}