<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Requirements and Limitations :: Airlock Microgateway</title>
    <link>https://docs.airlock.com/microgateway/5.2/requirements-and-limitations/</link>
    <description>Ensure that the following requirements are met to run Airlock Microgateway successfully. A valid license is required unless Airlock Microgateway is used in the Community Edition.&#xA;Compatibility overview The following table shows the general version range of different platforms Airlock Microgateway supports.&#xA;Platform Supported version range Official manufacturer documentation Kubernetes 1.34 – 1.37 Kubernetes changelog list on GitHub OpenShift 4.18 – 4.22 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 Kubernetes Gateway API support Version Description 1.2 – 1.6 (standard channel)1.6 (experimental channel)1 Kubernetes Gateway API versioning conceptKubernetes Gateway API implementation status list and version comparison 1 The Kubernetes Gateway API experimental channel is only required for some incubating features. See article Release Notes and Incubating Features.</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <atom:link href="https://docs.airlock.com/microgateway/5.2/requirements-and-limitations/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Resource Requirements</title>
      <link>https://docs.airlock.com/microgateway/5.2/requirements-and-limitations/resource-requirements/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.airlock.com/microgateway/5.2/requirements-and-limitations/resource-requirements/</guid>
      <description>Performance evaluation Understanding the resource footprint of Airlock Microgateway is essential for planning, deploying, and scaling production environments. To provide reliable guidance, we conducted performance benchmarks across a variety of configurations and traffic scenarios. These tests were designed to evaluate how CPU and memory usage scale under load and how different configuration profiles influence overall system behavior.</description>
    </item>
  </channel>
</rss>