BIG-IP Next for Kubernetes Software Images¶
The Big-IP Next for Kubernetes manifest file, Helm charts, Docker images, and other utilities are available via the F5 Artifact Registry (FAR). For more information, see Artifacts via F5 Artifact Registry (FAR). The following table provides a description of the software images included in this software release.
Note: The software image name and deployed container name may differ.
| Image | Version | Supported Architectures: x86 and ARM | Description |
|---|---|---|---|
| f5-lifecycle-operator | v1.7.8-0.3.37 | Yes | The f5-lifecycle-operator container manages the BIG-IP Next for Kubernetes installation. It continuously monitors the BnkGatewayClass CR, automatically redeploying any modified configurations to ensure optimal performance. Refer to F5 Lifecycle Operator. |
| f5ingress | v0.755.4-0.1.49 | Yes | The f5ingress container is the custom BIG-IP Next for Kubernetes Controller that watches the K8S API for CR updates, and configures the BIG-IP Next for Kubernetes TMM based on the update. |
| f5ing-tmm-pod-manager | v1.0.8 | Yes | The f5ing-tmm-pod-manager is a dedicated container that monitors and tracks TMM pods. It shares this information with any interested clients, f5-l4-controller and f5-l7-controller. |
| f5-coremond | v0.7.27-0.0.6 | Yes | The f5-coremond runs as a DaemonSet on BIG-IP Next for Kubernetes. It is designed to monitor and collect kernel core files (core dumps) from processes that terminate unexpectedly. Refer to Coremond. |
| f5-ipam-controller | v1.1.13-0.0.12 | Yes | The f5-ipam-controller manages the dual-stack IP addresses (IPv4 and IPv6) for the Gateway resource. |
| f5-fluentbit | v1.0.3-0.0.2 | Yes | The fluentbit container collects and forwards statistics to the f5-fluentd container. Multiple versions are included to support the different BIG-IP Next for Kubernetes containers. |
| opentelemetry-collector-contrib | 0.121.0 | Yes | The otel-collector container gathers metrics and statistics from the TMM Pods. Refer to OTEL Collector. |
| f5-license-helper | v0.12.5-1.0.4 | Yes | The f5-lic-helper communicates with the spk-cwc to determine the current license status of the cluster. |
| tmm-img | v10.14.0-0.1.9 | Yes | The f5-tmm container is a Traffic Management Microkernel (TMM) that proxies and load balances application traffic between the external and internal networks. |
| f5dr-img | v3.2.2 | Yes | The f5-tmm-routing container maintains the dynamic routing tables used by TMM. Refer to ZebOS ConfigMaps. |
| tmrouted-img | v2.1.7 | Yes | The f5-tmm-tmrouted container proxies and forwards information between the f5-tmm-routing and f5-tmm containers. |
| f5-debug-sidecar | v8.53.2-0.0.3 | Yes | The debug container provides diagnostic tools for viewing TMM's configuration, traffic processing statistics and gathering TMM diagnostic data. Refer to Debug Sidecar. |
| f5-blobd | v1.10.0-10.0.2 | Yes | The f5-blobd container allows loading binary large objects (BLOBs) into the TMM memory. It is required for AFM use-cases, like firewall and NAT. |
| f5-toda-tmstatsd | v1.11.12-0.0.3 | Yes | The f5-toda-stats container collects application traffic processing statistics from the f5-tmm container and saves the data to csv files, for processing and aggregation by observer pods and eventual export to the OTEL collector pod. |
| f5-toda-observer | v4.56.1-0.0.8 | Yes | The f5-toda-observer container comprises three pods: f5-observer-receiver, f5-observer, and f5-observer-operator. These pods work together to efficiently manage the high volume of statistics by collecting, aggregating, and exporting them to the OTEL Collector pod. |
| crd-conversion | v1.63.1-0.0.1 | Yes | The f5-crd-conversion container handles the automatic conversion of multiple CRD versions based on the specified namespace and version in the cluser, without affecting existing CRs. |
| f5-dssm-store | v5.0.7-0.0.3 | Yes | Contains two sets of software images; The f5-dssm-db containers that store shared, persisted session state data, and the f5-dssm-sentinel containers to monitor the f5-dssm-db containers. Refer to dSSM database. |
| f5-cert-client | v3.0.16-0.0.3 | Yes | The f5-cert-client container provides an interface for BIG-IP Next for Kubernetes components to request certificates from f5-cert-manager. Additionally, f5-cert-client can provide certificate rotation functionality for those SPK components. |
| rabbit | v0.5.5-0.0.2 | Yes | The rabbitmq-server container as a general message bus, integrating BIG-IP Next for Kubernetes CWC with the Controller Pod(s) for licensing purposes. |
| spk-csrc | v0.5.4-0.0.8 | Yes | The spk-csrc containers run as daemonset to enable the Egress traffic. |
| f5-fluentd | v2.0.6-0.0.1 | Yes | The f5-fluentd container collects statistics and logging data from the Controller, TMM and dSSM Pods. Refer to Fluentd Logging. |
| f5-csm-qkview | v0.10.21-0.0.3 | Yes | The f5-csm-qkview includes the qkview-orchestrator service, which manages requests from CWC to create or download qkview tar files. It communicates with qkview-collect, initiating the process of generating and downloading qkview tar files from containers within a designated namespace. |