F5 BIG-IP Container Ingress Services vs NGINX Gateway Fabric

F5 BIG-IP Container Ingress Services (CIS) connects Kubernetes and Red Hat OpenShift environments with F5 BIG-IP. It watches Kubernetes resources and adjusts BIG-IP configuration as applications change, while teams manage BIG-IP through Kubernetes or OpenShift command-line interfaces and APIs. CIS can send traffic from BIG-IP to clusters through NodePort or ClusterIP and supports F5 AS3 declarations. It provides HTTP and URI routing, load balancing, scaling, health monitoring, and Blue/Green or A/B traffic handling. F5 documents Ingress resources, OpenShift Routes, IngressLink coordination with NGINX Ingress Controller, and overlays including OpenShift SDN, Flannel, and Calico. BIG-IP data streams can export application and network statistics to tools such as Splunk. Installation is available through Helm or manual methods, with releases on Docker Hub and Red Hat Container Registry. The open-source plan is free, but requires a licensed BIG-IP system, a Kubernetes or OpenShift cluster, and AS3 installed on BIG-IP.

NGINX Gateway Fabric is a self-hosted Kubernetes implementation of the Gateway API, using NGINX as its data plane for load balancing, reverse proxying, and API gateway use cases. Its control plane translates Gateway API resources into NGINX configuration. Supported resource coverage includes GatewayClass, Gateway, HTTPRoute, GRPCRoute, ReferenceGrant, TLSRoute, TCPRoute, UDPRoute, and BackendTLSPolicy, though the support level varies by resource. Traffic features include HTTP and TLS routing, redirects, rewrites, request mirroring, session persistence, and rate limiting. Security documentation covers HTTPS with cert-manager, mutual TLS, basic authentication, OpenID Connect, external authentication, and JWT authentication. Monitoring examples use Prometheus and Grafana; tracing uses OpenTelemetry collectors, including Jaeger examples. The free NGINX Open Source data-plane plan costs nothing. Installation is available through Helm from an OCI registry or from source, with Gateway API resources installed beforehand. Version 2.7.2 requires Kubernetes 1.32 or later; documented images are available for amd64 and arm64. Support is directed to GitHub issues and the NGINX Community Forum.