The Gateway API project is the successor to the Ingress API. However, it does not include the Ingress resource (the closest parallel is the HTTPRoute). As a result, a one-time conversion from your existing Ingress resources to the relevant Gateway API resources is necessary.

This guide will help you with the conversion. It will:

• Explain why you may want to switch to the Gateway API.
• Describe the key differences between the Ingress API and the Gateway API.
• Map Ingress features to Gateway API features.
• Show an example of an Ingress resource converted to Gateway API resources.
• Mention ingress2gateway for automatic conversion.

At the same time, it will not prepare you for a live migration or explain how to convert some implementation-specific features of your Ingress controller. Additionally, since the Ingress API only covers HTTP/HTTPS traffic, this guide does not cover the Gateway API support for other protocols.