For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

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.

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

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.

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

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.

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.

NGF

Further Reading

Last updated