This document provides general information regarding the F5 Integration for OpenShift. For deployment and usage instructions, please refer to the guides below.
The BIG-IP Controller for OpenShift enables use of a BIG-IP device in OpenShift. Because OpenShift has a native Kubernetes integration, the F5 Integration for OpenShift utilizes the same controller as the F5 Integration for Kubernetes. In OpenShift, you can use the BIG-IP Controller to use a BIG-IP device(s) to:
In OpenShift clusters, the Kubernetes NodeList records status for all nodes registered with the master. Because the BIG-IP Controller integrates with the cluster network, it can access the NodeList in OpenShift’s underlying Kubernetes API server and watch it for changes. The BIG-IP Controller creates/updates FDB (Forwarding DataBase) entries for the configured VXLAN tunnel according to the NodeList. This ensures the BIG-IP Controller only makes VXLAN requests to reported nodes.
As a function of the BIG-IP VXLAN, the BIG-IP device only communicates with healthy cluster nodes. The BIG-IP device does not attempt to route traffic to an unresponsive node, even if the node remains in the NodeList.
You can also set up BIG-IP health monitors for OpenShift Services.
In OpenShift, the BIG-IP Controller can manage BIG-IP objects for routes.
See manage OpenShift Routes with the BIG-IP Controller for configuration instructions.
Setting up OpenShift Route resources provides the following functionality:
The table below shows what BIG-IP configurations the BIG-IP Controller applies for common admin tasks in OpenShift.
|User action||Controller action|
|Create OpenShift Route||
|Delete all Routes||
Refer to the docs listed below for setup and configuration instructions.