BIG-IP Next for Kubernetes (DPU) software images¶
You can download the BIG-IP Next for Kubernetes manifest, Helm charts, container images, and related tools from the F5 Artifact Registry (FAR).
The tables below describe the container images included in this release. For container image versions, see Download Artifacts via F5 Artifact Registry (FAR).
Note
The software image name and deployed container name may differ. All container images listed on this page support x86 and ARM architectures.
Core Management Containers¶
Image |
Description |
|---|---|
f5-lifecycle-operator |
Installs and manages BIG-IP Next for Kubernetes. It monitors the CNEInstance Custom Resource (CR) and reapplies changes to keep the deployment in the desired state. See F5 Lifecycle Operator. |
f5ingress |
It is the custom BIG-IP Next for Kubernetes controller. It watches the Kubernetes API for CR updates and configures Traffic Management Microkernel (TMM) based on the updates. |
f5ing-tmm-pod-manager |
Tracks and monitors TMM pods. It shares pod status with clients such as f5-l4-controller and f5-l7-controller. |
f5-license-helper |
Communicates with spk-cwc to check and report the cluster’s current license status. |
crd-conversion |
Automatically converts multiple CRD versions for the configured namespace and version in the cluster, without changing existing custom resources |
Network and IP Management¶
Image |
Description |
|---|---|
f5-ipam-controller |
Manages dual-stack (IPv4/IPv6) IP addresses for the Gateway resource. |
Monitoring and Statistics¶
Image |
Description |
|---|---|
f5-fluentbit |
Collects and forwards statistics to f5-fluentd. Multiple versions are provided to support different BIG-IP Next for Kubernetes containers. |
opentelemetry-collector-contrib |
The otel-collector gathers metrics and statistics from the TMM Pods. See OTEL Collector. |
f5-coremond |
Runs as a DaemonSet to monitor for unexpected process exits and collect kernel core files (core dumps). See Coremond. |
f5-toda-tmstatsd |
Collects traffic-processing stats from f5-tmm and saves them to CSV. Additionally it prepares the CSV for processing and aggregation by observer pods and export to the OTEL collector pod. |
f5-toda-observer |
Comprises three pods: f5-observer-receiver, f5-observer, and f5-observer-operator. These pods work together to collect, aggregate, and export statistics to the OTEL collector pod. |
f5-fluentd |
Collects logs and statistics from the controller, TMM, and distributed Session State Management (dSSM) pods. See Fluentd Logging. |
f5-csm-qkview |
Provides qkview services. It includes qkview-orchestrator (manages requests from Cluster Wide Controller (CWC) to create or download qkview tar files) and qkview-collect (collects data from containers in a target namespace and packages it as a tar file). |
Traffic Management¶
Image |
Description |
|---|---|
tmm-img |
The f5-tmm container is a TMM. It proxies and load-balances application traffic between external and internal networks. |
tmrouted-img |
The f5-tmm-tmrouted container proxies and forwards information between the f5-tmm-routing and f5-tmm containers. |
f5-blobd |
Loads Binary Large Objects (BLOBs) into TMM memory. It is required for some Advanced Firewall Manager (AFM) use cases (for example, firewall and NAT) |
f5dr-img |
The f5-tmm-routing container maintains the dynamic routing tables used by TMM. Refer to ZebOS ConfigMaps. |
Diagnostic Tools¶
Image |
Description |
|---|---|
f5-debug-sidecar |
Provides diagnostic tools to view TMM configuration, traffic-processing statistics, and collect TMM diagnostic data. See Debug Sidecar. |
Session and Data Storage¶
Image |
Description |
|---|---|
f5-dssm-store |
Includes two image sets: f5-dssm-db (stores shared, persisted session-state data) and f5-dssm-sentinel (monitors the f5-dssm-db database containers). See dSSM database. |
Security and Certificates¶
Image |
Description |
|---|---|
f5-cert-client |
Provides an interface for BIG-IP Next for Kubernetes components to request certificates from f5-cert-manager. It can also rotate certificates for supported SPK components. |
Communication and Messaging¶
Image |
Description |
|---|---|
rabbit |
Runs rabbitmq-server as a message bus. It connects BIG-IP Next for Kubernetes CWC with controller pod(s), including for licensing workflows. |
Additional Support Containers¶
Image |
Description |
|---|---|
spk-csrc |
Runs as a DaemonSet to enable egress traffic. |
spk-cwc |
Manages and serves licenses for BIG-IP Next for Kubernetes controllers in the cluster. It also provides a debug API for troubleshooting without shell access, and a qkview API for collecting and exporting cluster diagnostics. |