VirtualGateway

Proto: virtual_gateway.proto

Package: networking.gloo.solo.io

Types:

• ListenerRouteTable

• TLSConfig

• TLSConfig.Files

• TLSConfig.Parameters

• VirtualGatewayReport

• VirtualGatewayReport.WorkspacesEntry

• VirtualGatewaySpec

• VirtualGatewaySpec.Listener

• VirtualGatewaySpec.Listener.ExternalServiceFilter

• VirtualGatewaySpec.Listener.HTTPServer

• VirtualGatewaySpec.Listener.RouteTableFilter

• VirtualGatewaySpec.Listener.TCPServer

• VirtualGatewayStatus

• TLSConfig.Parameters.ProtocolVersion

• TLSConfig.TLSMode

ListenerRouteTable link

ListenerRouteTable represents an association between a RouteTable and a particular VirtualGateway listener.

TLSConfig link

TLSConfig contains the options necessary to configure a listener to use TLS

TLSConfig.Files link

TLSConfig.Parameters link

General TLS parameters. See the envoy docs for more information on the meaning of these values.

VirtualGatewayReport link

VirtualGatewayReport.WorkspacesEntry link

VirtualGatewaySpec link

VirtualGateway represents a logical gateway configuration served by Gateway workloads within the same workspace. The specification describes a set of ports that the virtual gateway listens for incoming or outgoing HTTP/TCP connections, the type of protocol to use, SNI configuration etc.

For example, the following VirtualGateway resource configures the gateway to listen for incoming HTTP requests on port 80, and delegate the route configuration of the ‘*.bookinfo.com’ hostname to be provided by the bookinfo workspace. The VirtualGateway is applied to a specific set of gateway pods/VMs with the app:my-gateway-controller label within the same workspace as the VirtualGateway resource.

  apiVersion: networking.gloo.solo.io/v2
kind: VirtualGateway
metadata:
  name: my-gateway
  namespace: some-config-namespace
  labels:
    workspace.solo.io/exported: 'true'
spec:
  workloads:
    - selector:
        labels:
          app: my-gateway-controller
  listeners:
    - port:
        number: 80
      allowedRouteTables:
        - host: '*.bookinfo.com'
          selector:
            workspace: bookinfo
  

For example, the following VirtualGateway resource configures the gateway to listen for incoming HTTP requests on port 80, delegate any *.foo.com request to the HTTPRouteTable resource(s) provided by the foo-ws workspace. Further, on the same port 80, it also delegates any *.bar.com request to the route configurations provided by the bar-ws workspace.

  apiVersion: networking.gloo.solo.io/v2
kind: VirtualGateway
metadata:
  name: my-gateway
  namespace: some-config-namespace
  labels:
    workspace.solo.io/exported: 'true'
spec:
  workloads:
    - selector:
        labels:
          app: my-gateway-controller
  listeners:
    - port:
        number: 80
      allowedRouteTables:
        - host: '*.foo.com'
          selector:
            workspace: foo-ws
        - host: '*.bar.com'
          selector:
            workspace: bar-ws
  

For example, the following VirtualGateway resource configures the gateway to act as a load balancer listening on port 80 and 9080 (http), 443 (https), and 9443(https) for ingress. The VirtualGateway resource is applied to a specific set of gateway pods/VMs with the app: my-gateway-controller label within the same workspace. The route table(s) associated with each port 80, 9443 and 443 must be provided by the foo-ws workspace, with hosts that match *.foo.com. The route table(s) for port 9080 must be provided by the bar-ws workspace with hosts that match *.bar.com.

  apiVersion: networking.gloo.solo.io/v2
kind: VirtualGateway
metadata:
  name: my-gateway
  namespace: some-config-namespace
  labels:
    workspace.solo.io/exported: 'true'
spec:
  workloads:
    - selector:
        labels:
          app: my-gateway-controller
  listeners:
    - port:
        number: 80
      httpsRedirect: true
      allowedRouteTables:
        - host: '*.foo.com'
          selector:
            workspace: foo-ws
    - port:
        number: 443
      tls:
        mode: SIMPLE
        files:
          privateKey: /etc/certs/privatekey.pem
          serverCert: /etc/certs/servercert.pem
      allowedRouteTables:
        - host: '*.foo.com'
          selector:
            workspace: foo-ws
    - port:
        number: 9443
      tls:
        mode: SIMPLE
        secretName: my-secret
      allowedRouteTables:
        - host: '*.foo.com'
          selector:
            workspace: foo-ws
    - port:
        number: 9080
      allowedRouteTables:
        - host: '*.bar.com'
          selector:
            workspace: foo-ws
  

For example, the following VirtualGateway resource configures the gateway to listen for incoming HTTP requests on port 80, delegate any *.foo.com request to the HTTPRouteTable resource(s) provided by the foo-ws workspace. This routeTable is restricted to using CloudProvider functionality which routes to cloud functions backend-function-* in region us-east-2 and which assume the dev-team-B-* IAM role.

  apiVersion: networking.gloo.solo.io/v2
kind: VirtualGateway
metadata:
  name: my-gateway
  namespace: some-config-namespace
  labels:
    workspace.solo.io/exported: 'true'
spec:
  workloads:
    - selector:
        labels:
          app: my-gateway-controller
  listeners:
    - port:
        number: 80
      allowedRouteTables:
        - host: '*.foo.com'
          selector:
            workspace: foo-ws
  

VirtualGatewaySpec.Listener link

VirtualGatewaySpec.Listener.ExternalServiceFilter link

Filter ExternalServices which can attach to a VGW by host name.

VirtualGatewaySpec.Listener.HTTPServer link

HTTP server indicates HTTP routes will be served for RouteTables which select this gateway.

VirtualGatewaySpec.Listener.RouteTableFilter link

Filter route tables which can attach to a VGW by host name as well as an object selector.

VirtualGatewaySpec.Listener.TCPServer link

VirtualGatewayStatus link

TLSConfig.Parameters.ProtocolVersion link

TLSConfig.TLSMode link