Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

F5 BIG-IP Container Ingress Services review

Free#22 of 28 in Kubernetes Ingress Controllers

A capable self-hosted ingress controller for teams already running licensed BIG-IP.

7.1/10Editor score
F5 BIG-IP Container Ingress Services7.1 Visit F5

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

F5 BIG-IP Container Ingress Services (CIS) is an open-source controller that connects Kubernetes and OpenShift orchestration APIs with F5 BIG-IP. It watches container environment changes and dynamically configures BIG-IP application objects, including virtual servers and pools. Teams running Kubernetes, Red Hat OpenShift, or VMware Tanzu can use it for HTTP and HTTPS routing, service load balancing, and ingress management, provided they have an active, licensed BIG-IP system.

Its strongest differentiator is the breadth of BIG-IP integration exposed through Kubernetes-native configuration. CIS supports Kubernetes Ingress resources, OpenShift Routes, and custom resources such as VirtualServer, TransportServer, TLSProfile, and Policy. Helm-chart installation is available for Kubernetes and OpenShift. Existing BIG-IP WAF policies can be attached through Policy or VirtualServer resources, while multi-cluster traffic distribution can use ratios and weights. TLS can rely on BIG-IP SSL profiles or Kubernetes TLS Secrets.

The main trade-off is ecosystem dependence. CIS is not a standalone ingress layer: its deployment and value are tied to F5 BIG-IP, and the operating model remains self-hosted. That makes it a focused choice for organizations standardizing on BIG-IP security, traffic management, and application delivery. Teams without an active licensed BIG-IP system, or those seeking an ingress controller independent of a specific appliance ecosystem, should consider a different product category fit.

F5 BIG-IP Container Ingress Services pros and cons

  • Where it wins
    • Manages L4/L7 BIG-IP services from orchestration changes
    • Supports Kubernetes Ingress, OpenShift Routes, and custom resources
    • Adds WAF policies, multi-cluster weights, and TLS options
  • Where it doesn't
    • Requires an active, licensed BIG-IP system
    • Deployment and operations remain self-hosted
    • Its value is closely tied to the F5 BIG-IP ecosystem

F5 BIG-IP Container Ingress Services fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update