F5 BIG-IP Container Ingress Services vs N42 Gateway
F5 BIG-IP Container Ingress Services
clouddocs.f5.comN42 Gateway
github.comSide by side
| Figure | F5 BIG-IP Container Ingress Services | N42 Gateway |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Linux | — | Yes |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Kubernetes Ingress Controllers | 7.8 (#10) | 7.1 (#19) |
| Purpose | CIS integrates container orchestration environments with F5 BIG-IP to dynamically create L4/L7 services and load balance traffic as container applications change. | N42 Gateway is a Kubernetes Ingress and Gateway API controller that configures HAProxy to route external requests to in-cluster applications. |
Plans
F5 BIG-IP Container Ingress Services
- Open-source softwareFree
In their own words
F5 BIG-IP Container Ingress Services
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.
N42 Gateway
N42 Gateway has no write-up on Specifiction yet; its figures are above.