F5 IngressLink

The F5 IngressLink solution addresses modern app delivery at scale. IngressLink is a resource definition defined between BIG-IP Next and NGINX using F5 Container Ingress Service and NGINX Ingress Service.

The F5 IngressLink is the true integration between BIG-IP Next and NGINX technologies. F5 IngressLink was built to support customers with modern, container application workloads that use both BIG-IP Next Container Ingress Services and NGINX Ingress Controller for Kubernetes. It is an elegant control plane solution that offers a unified method of working with both technologies from a single interface—offering the best of BIG-IP Next and NGINX and fostering better collaboration across NetOps and DevOps teams. The diagram below demonstrates this use case.

This architecture diagram demonstrates the IngressLink solution:

_images/F5Ingresslink.png

Parameters

Parameter Type Required Default Description
ipamLabel String Optional N/A FIC allocates IP addresses from an IPAM system’s address pool
virtualServerAddress String Yes N/A IPAddress of Virtual server
iRules List Yes N/A List of iRules which needs to be attached to virtual server
partition String Optional N/A BIG-IP Next Partition

Note

You can use IPAM controller to configure and manage virtual server addresses in IngressLink by using ipamLabel. If you are using IPAM, virtualServerAddress is not required.