# NGINX (retired) (/docs/runtime/components/nginx)



> **Note**
> NGINX was used in previous versions of BullSequana AI as the primary ingress controller. It has been replaced by [Gateway API (Envoy Gateway)](/docs/runtime/components/gateway-api) starting with version 1.2.0. This page is retained for reference.

Component Category [#component-category]

Networking / reverse proxy

Component Description [#component-description]

`NGINX Ingress Controller` was a Kubernetes ingress controller based on NGINX. It served as the primary ingress path for all platform endpoints in earlier versions of the platform.

Why It Was Used [#why-it-was-used]

In previous versions of BullSequana AI, NGINX was used to front internal services, manage request forwarding, and provide TLS termination for platform endpoints. It has been replaced by `Gateway API` (`Envoy Gateway`), which provides a standards-based routing model using the Kubernetes Gateway API specification.

Learn More [#learn-more]

* [NGINX Ingress Controller documentation](https://kubernetes.github.io/ingress-nginx/)
* [kubernetes/ingress-nginx on GitHub](https://github.com/kubernetes/ingress-nginx)

Replaced By [#replaced-by]

* [Gateway API (Envoy Gateway)](/docs/runtime/components/gateway-api)