Requirements and limitations

Ensure the following requirements are met in order to run Airlock Microgateway successfully. Note that in addition to the following requirements, a valid license is required to operate Airlock Microgateway.

 
Functional limitation
  • Mixing different versions like Airlock Microgateway Operator in version 4.x and Microgateway Engine in version 4.y is not supported.
  • WebSocket support is limited to HTTP/1.1.

Compatibility overview

The following table shows the general version range of different platforms Airlock Microgateway supports.

Platform

Supported version range

Official manufacturer documentation

Kubernetes (K8s)

1.31 – 1.33

Kubernetes Gateway API

  • 1.0 – 1.3 (standard channel)
  • 1.3 (experimental channel)1

OpenShift

  • 4.14
  • 4.16 – 4.19

The link below opens the latest OpenShift release notes. To access the release notes of a different version, use the selector drop-down menu on the page.

OpenShift Container Platform release notes

OpenShift Service Mesh

2.6

The link below opens the latest OpenShift release notes. To access the release notes of a different OpenShift version, use the selector drop-down menu on the page. OpenShift Service Mesh release notes can be searched within the documentation.

OpenShift Container Platform release notes

    Istio Service Mesh

    1.25 – 1.27

    Anthos Service Mesh

    1.25 – 1.26

    1

    The K8s Gateway API experimental channel is only required for some incubating features, such as upstream TLS support between the Microgateway Engine and the application Service. See article Release notes and incubating features.

     
    Info

    For compatibility with Kubernetes releases with Istio, Anthos, and OpenShift Service Meshes, see the official manufacturer's documentation.

    Additional components

    Airlock Microgateway requires the following components to run:

    Component

    Tested version

    Description

    cert-manager

    1.18

    The cert-manager is required to secure the connection between Kubernetes API server to the Microgateway Operator Webhook.

    To install the cert-manager, follow the manual: installation of the cert-manager

    Redis

    8.x

    When session handling is enabled, a Redis instance is required to persist session data.

    For detailed setup and configuration instructions, refer to the official Redis documentation: Redis Docs

    Network communication

    The following network communication is required:

    From

    To service

    To namespace

    To port

    To protocol

    Microgateway Engine container

    airlock-microgateway-operator-xds

    <Microgateway Operator namespace>

    13377

    TCP