NGINX (retired)
Ingress controller used in previous versions of the platform, replaced by Gateway API.
Note NGINX was used in previous versions of BullSequana AI as the primary ingress controller. It has been replaced by Gateway API (Envoy Gateway) starting with version 1.2.0. This page is retained for reference.
Component Category
Networking / reverse proxy
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
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.