https://docs.airlock.com/microgateway/5.2/release-and-support/ Release lifecycles Patch releases for minor versions will be served for 9 months from the release date of the respective minor version. End-of-support dates (EOS) Supported releases are covered by the Airlock support process. That is, customers and partners may open support cases for these versions, and our support team will investigate these issues. Hugo en-US https://docs.airlock.com/microgateway/5.2/release-and-support/release-notes-and-incubating-features/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.airlock.com/microgateway/5.2/release-and-support/release-notes-and-incubating-features/ Release notes Airlock Microgateway release notes are published on GitHub. Info Read the release notes carefully and pay attention to breaking changes or required actions. Incubating features Feature name Description Limitations Downstream HTTP/3 With Airlock Microgateway 4.8, we introduce support for HTTP/3 downstream connections. QUIC connection migration and upstream HTTP/3 are currently not supported. HTTPRoute Retry With Airlock Microgateway 5.1, we introduced the Gateway API experimental feature HTTPRoute retries. It allows you to configure retries for unsuccessful requests to backends. HTTPRoute retries has been implemented with Kubernetes Gateway API 1.6.x-experimental. To use this feature, you must install the Gateway API experimental channel. XBackend With Airlock Microgateway 5.2, we introduced the Gateway API experimental feature XBackend. It allows you to reference backends beyond Kubernetes Services, such as external hostnames outside the cluster, as HTTPRoute targets. XBackend has been implemented with Kubernetes Gateway API 1.6.x-experimental. To use this feature, you must install the Gateway API experimental channel.