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.
The following table shows the general version range of different platforms Airlock Microgateway supports.
Platform | Supported version range | Official manufacturer documentation |
|---|---|---|
Kubernetes (K8s) |
| |
Kubernetes Gateway API |
| |
OpenShift |
| 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 Service Mesh |
| 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. |
Istio Service Mesh |
| |
Anthos Service Mesh |
|
| 1 | The K8s Gateway API experimental channel is only required for the incubating feature of upstream TLS support between the Microgateway Engine and the application Service. See article Release notes and incubating features in Airlock Microgateway. |
For compatibility with Kubernetes releases with Istio, Anthos, and OpenShift Service Meshes, see the official manufacturer's documentation.
Airlock Microgateway requires the following components to run:
Component | Tested version | Description |
|---|---|---|
cert-manager | v1.16 | 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 |
The following network communication is required:
From | To service | To namespace | To port | To protocol |
|---|---|---|---|---|
Microgateway Engine container |
|
|
|
|