Use the BIG-IP Controller as a Kubernetes Ingress Controller¶
This document provides an overview of how you can use the BIG-IP Controller for Kubernetes as an Ingress Controller in Kubernetes. For set-up instructions, see Using the BIG-IP Controller as an Ingress controller.
Using Multiple Ingress Controllers¶
The BIG-IP Controller automatically manages all Ingress resources that don’t have an
Because the Ingress resource’s
ingress.class property is empty by default, the BIG-IP Controller will automatically try to manage all Ingress resources residing in the namespace(s) it watches. The BIG-IP Controller ignores Ingress resources that have any
ingress.class other than “f5”.
If you’re using another Ingress Controller to manage Kubernetes Ingress resources:
ingress.classto “f5” in all Ingress resources you want the BIG-IP Controller to manage.
ingress.classas appropriate in Ingress resources managed by other Ingress Controllers.
IP address assignment¶
The Controller creates one virtual server for each unique IP address listed in an Ingress resource. You can manage IP address assignment using the options below.
See the k8s-bigip-ctlr configuration parameters table for more information about the required settings.
Use BIG-IP SNAT Pools and SNAT automap¶
By default, the BIG-IP Controller uses BIG-IP Automap SNAT for all of the virtual servers it creates.
k8s-bigip-ctlr v1.5.0 forward, you can designate a specific SNAT pool in the Controller Deployment instead of using SNAT automap.
In environments where the BIG-IP connects to the Cluster network, the self IP used as the BIG-IP VTEP serves as the SNAT pool for all origin addresses within the Cluster. The subnet mask you provide when you create the self IP defines the addresses available to the SNAT pool.
See BIG-IP SNATs and SNAT automap for more information.
Use DNS lookup¶
The BIG-IP Controller uses DNS lookup to resolve hostnames by default. The BIG-IP Controller attempts to resolve the first hostname provided in the
spec.rules.host section of the Ingress resource. It then assigns the resolved host’s IP address to the Ingress’ virtual server.
Use an IPAM system¶
If you want to assign IP addresses using an IPAM system, use the BIG-IP Controller to create unattached pools. To do so, just omit the
virtual-server.f5.com/ip= annotation from your Ingress resource.
You can then add the virtual-server annotation to the Ingress using the IP address selected by the IPAM system. The BIG-IP Controller will create a new virtual server with the selected IP address and attach the previously-created pool(s) to it.
- Using the BIG-IP Controller as an Ingress controller
- Manage your BIG-IP virtual servers
- Attaching Virtual Servers to Services for L4 ingress and L7 ingress on non-standard ports