Managed BIG-IP objects

You can deploy BIG-IP objects for Services and Ingresses in Kubernetes. In OpenShift, you can deploy BIG-IP objects for Services and Routes. The BIG-IP Controller can create, update, remove, and/or manage BIG-IP objects as noted in the table below.

Type Create New Object Use Existing Object Notes
health monitor X X

The BIG-IP Controller can use existing health monitors for all supported Kubernetes resources.

The BIG-IP Controller can create health monitors for certain types of Kubernetes resources, as described in the deployment guides.

iApp   X The BIG-IP Controller can deploy any iApp that already exists on the BIG-IP system.
node X   Applies to all supported Kubernetes resources.
partition   X The BIG-IP Controller cannot create or destroy BIG-IP partitions.
pool X   Applies to all supported Kubernetes resources.
pool member X   Applies to all supported Kubernetes resources.
self IP   X Applies to all supported Kubernetes resources.
profiles
  HTTP   X Kubernetes Ingress resources (L7) only
  SSL X X Supported functionality varies by resource and platform. See note below.
  TCP   X F5 Resources (L4) only
  UDP   X F5 Resources (L4) only
traffic policy X   Kubernetes Ingress resources (L7) only; the Controller creates a BIG-IP traffic policy to use for routing.
virtual server X   Applies to all supported Kubernetes resources.

Note

The BIG-IP Controller support for SSL profiles varies based on resource type:

BIG-IP Controller support for all profiles applies to basic profiles only. Optimized and/or customized versions aren’t supported.

Object Naming Convention

The BIG-IP Controller prefaces all BIG-IP virtual server objects with [namespace]_[resource-name]. For example, if default is the namespace and k8s.vs is the ConfigMap name, the object preface is default_k8s.vs_173.16.2.2:80.

High-availability and Multi-tenancy

If you’re using a BIG-IP device pair or cluster, F5 recommends deploying multiple BIG-IP Controller instances – one Controller per BIG-IP device. You can also deploy multiple Controller instances to manage separate BIG-IP partitions (for example, one Controller:one namespace:one partition).