> For the complete documentation index, see [llms.txt](https://academy.cegedim.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.cegedim.cloud/compute/containers-k8s/k8s-features/gateway-api.md).

# Gateway API

Kubernetes Gateway API support on cegedim.cloud — NGF, Traefik, and Istio implementations

## Overview

Kubernetes Gateway API is the official successor to the Ingress API. It is expressive, role-oriented, and implementation-agnostic — the same HTTPRoute manifests work across all supported implementations.

{% hint style="info" %}
**Why move away from NGINX Ingress Controller?** The upstream project (`kubernetes/ingress-nginx`) has reached end-of-life. Security patches will be provided for a limited period only. Gateway API is the Kubernetes SIG-Network standard replacement.
{% endhint %}

Key advantages over the legacy Ingress API:

* **Standard API**: `HTTPRoute`, `GRPCRoute`, `TLSRoute` — defined by Kubernetes SIG-Network
* **Role separation**: platform team owns the `Gateway`, application teams own `HTTPRoute` resources in their own namespaces
* **Portable**: same manifests work across NGF, Traefik, Istio, Envoy Gateway
* **Extensible**: policy attachment (timeouts, retries, auth) without proprietary annotations

## Implementations on cegedim.cloud

At cluster creation, customers choose one of three ingress stacks. All three support Gateway API:

| Implementation                 | Gateway API Support                      | Notes                                                  |
| ------------------------------ | ---------------------------------------- | ------------------------------------------------------ |
| **Traefik**                    | Native (v3+)                             | Full Gateway API support since Traefik v3              |
| **Istio**                      | Native                                   | Full Gateway API support as part of the service mesh   |
| **NGINX Gateway Fabric (NGF)** | Yes — replacing NGINX Ingress Controller | NGF will replace the legacy `ingress-nginx` controller |

{% hint style="warning" %}
**NGINX Ingress Controller** (ingress-nginx) is the current default for existing clusters and is being **replaced by NGF (NGINX Gateway Fabric)**. New clusters will use NGF. Existing clusters will be migrated — see the [Migrate to NGF Gateway API](/compute/containers-k8s/k8s-get-started/k8s-gateway-api-migration.md).
{% endhint %}

### Traefik

Traefik v3 supports Gateway API natively. If your cluster was provisioned with Traefik, you can create `HTTPRoute`, `GRPCRoute`, and `TLSRoute` resources directly — no additional setup is needed.

{% embed url="<https://doc.traefik.io/traefik/routing/providers/kubernetes-gateway/>" %}

### Istio

Istio supports Gateway API as its primary ingress model, with full support for both **sidecar** and **ambient** mesh modes. It can be used as the sole ingress stack (chosen at cluster creation) or installed additionally on clusters using NGF or Traefik.

[Istio](/compute/containers-k8s/k8s-features/gateway-api/gateway-api-istio.md)

{% hint style="info" %}
If Istio is deployed alongside NGF on the same cluster, there is no conflict risk — unlike Envoy Gateway, which shares the Envoy data plane with Istio.
{% endhint %}

### NGINX Gateway Fabric (NGF)

NGF is the Gateway API implementation that will replace the legacy NGINX Ingress Controller on cegedim.cloud. It uses NGINX as its data plane, which provides a familiar operational model for teams already using ingress-nginx.

If you are currently running NGINX Ingress Controller on an existing cluster and need to migrate to NGF, refer to the step-by-step [Migrate to NGF Gateway API](/compute/containers-k8s/k8s-get-started/k8s-gateway-api-migration.md).

[NGF](/compute/containers-k8s/k8s-features/gateway-api/gateway-api-ngf.md)

## Further Reading

{% embed url="<https://gateway-api.sigs.k8s.io/>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.cegedim.cloud/compute/containers-k8s/k8s-features/gateway-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.