F5’s Container Integrations provide the ability to dynamically allocate L4-L7 services in container orchestration environments. The BIG-IP Container Connectors (“CCs”) introduce BIG-IP services for North-South traffic, while the Application Services Proxy provides services for East-West traffic.
F5’s Container Connectors (‘CCs’) understand the container orchestration environment (‘COE’). The CCs provide PaaS-native integrations for F5 BIG-IP devices and the Application Services Proxy (‘ASP’).
Configures ASPs in a Kubernetes cluster, serving East-West traffic.
Replaces the standard
|marathon-asp-ctlr||Provisions and configures ASPs in a an Apache Mesos Marathon cluster, serving East-West traffic.|
|cf-bigip-ctlr||Integrates BIG-IP as an Application Delivery Controller (ADC) in Pivotal Cloud Foundry, serving North-South traffic.|
|k8s-bigip-ctlr||Configures a BIG-IP device to expose applications in a Kubernetes cluster as virtual servers, serving North-South traffic.|
|marathon-bigip-ctlr||Configures a BIG-IP device to expose applications in an Apache Mesos Marathon cluster as virtual servers, serving North-South traffic.|
Each CC is uniquely suited to its specific container orchestration environment and purpose, utilizing the architecture and language appropriate for the environment. Application Developers interact with the platform’s API; the container connectors watch the API for certain events, then act accordingly.
The Container Connector is stateless: the inputs are the container orchestration environment’s config, the BIG-IP device or ASP instance config, and its own config (provided by the container orchestration environment). This means an instance of a Container Connector can be readily discarded. Migrating a CC is as easy as destroying it in one place and spinning up a new one somewhere else. Wherever a Container Connector runs, it always watches the API and attempts to bring the BIG-IP, or ASP, up to date with the most recent applicable configurations.