Exposing Workloads Using Gateway API ​
The Istio module installs the Kubernetes Gateway API CustomResourceDefinitions (CRDs). This tutorial shows how to expose an HTTP workload using a Gateway resource and an HTTPRoute.
Prerequisites ​
- You have the Istio module added.
- You can use a Kyma domain (the default domain provided by your Kyma cluster, managed automatically by Gardener) or a custom domain (your own domain name that you manage through an external DNS provider). For the custom domain approach, you need credentials for a DNS provider supported by Gardener. For the list of supported providers, see External DNS Management Guidelines.
Context ​
In this tutorial, you expose a sample HTTPBin Service outside the cluster using the Kubernetes Gateway API. You can choose between two approaches: using the Kyma domain (managed automatically by Gardener) or using your own custom domain. In both cases, you create a Gateway resource that defines the entry point for external traffic, and an HTTPRoute that routes incoming traffic to the HTTPBin Service. Istio acts as the Gateway API controller and provisions the infrastructure needed to route traffic. To verify the setup, you call the service and confirm it returns a 200 OK response.
For details on Gateway API CRD management in the Istio module, see Gateway API CRDs Management.