GatewayParameters

apiVersion: microgateway.airlock.com/v1alpha1
kind: GatewayParameters
metadata:
  name: gateway-parameters-example
spec:
  # Enable debug logging
  logging:
    level: debug

  kubernetes:
    # Expose the Gateway using a service with an internet-facing AWS Network Load Balancer
    service:
      type: LoadBalancer
      annotations:
        service.beta.kubernetes.io/aws-load-balancer-type: external
        service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip
        service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing

    deployment:
      replicas: 3

      strategy:
        type: RollingUpdate
        rollingUpdate:
          maxUnavailable: 1

      # Schedule the Airlock Microgateway Engine pods on a specific instance type and across availability zones
      placement:
        nodeSelector:
          node.kubernetes.io/instance-type: m3.medium
        topologySpreadConstraints:
          - maxSkew: 1
            topologyKey: topology.kubernetes.io/zone
            whenUnsatisfiable: ScheduleAnyway

      # Specify Volumes for the Airlock Microgateway Gateway deployment
      volumes:
        - name: vol-1
          emptyDir: {}

      engineContainer:
        # Set resource restrictions to apply to the Airlock Microgateway Engine container
        resources:
          limits:
            cpu: 500m
            memory: 128Mi
          requests:
            cpu: 10m
            memory: 40Mi
        # Specify VolumeMounts for the Airlock Microgateway Engine container
        volumeMounts:
          - name: vol-1
            mountPath: /tmp/data
        securityContext:
          # Specify additional capabilities assigned to the Airlock Microgateway Engine container
          capabilities:
            add: ["BPF"]

  defaults:
    customResponses:
      # Customize all direct error responses sent by the Gateway
      local:
        - statusCodeCondition:
            matcher:
              exact: 401
          customResponseRef:
            name: custom-401
        - statusCodeCondition:
            matcher:
              exact: 404
          customResponseRef:
            name: custom-404
        - statusCodeCondition:
            matcher:
              range:
                start: 400
                end: 499
          customResponseRef:
            name: custom-400
        - statusCodeCondition:
            matcher:
              range:
                start: 500
                end: 599
          customResponseRef:
            name: custom-5xx
      # Replace upstream error responses with custom responses
      upstream:
        - responseConditions:
            statusCode:
              matcher:
                range:
                  start: 400
                  end: 499
          customResponseRef:
            name: upstream-4xx
        - responseConditions:
            statusCode:
              matcher:
                range:
                  start: 500
                  end: 599
          customResponseRef:
            name: upstream-5xx

    sessionHandlingRef:
      name: session-handling-example

    telemetryRef:
      name: telemetry-example

    downstream:
      # Configure 'remoteIP' extraction.
      remoteIP:
        xff:
          numTrustedHops: 1