BIG-IP Next for Kubernetes (DPU) 2.2.1 release notes

About this release

Introduction

These release notes describe the differences between BIG-IP Next for Kubernetes (DPU) 2.2.0 and 2.2.1.

Supported container-orchestration platforms

This release is officially supported on these container-orchestration platforms and versions:

Platform

Version

Recommended Helm version

Kubernetes

1.30.10

3.18

Kubernetes

1.30.14

3.18

Security updates

(No security updates)

New features

(No new features)

Enhancements

Configure SNAT type

Added support to configure Gateway SNAT behavior via the infrastructure annotation spec.infrastructure.annotations[“k8s.f5.com/snat-type”]. For more information, see BNK Gateway parameters

Enable DSSM component as shared resource

Added support for a shared DSSM deployment by enabling the .values.sharedDssm parameter. When set to true, a single DSSM is installed in the shared component namespace (defaulting to the FLO namespace) and used by all CNEInstance components in the cluster, rather than creating a DSSM per instance. For more information, see F5 Lifecycle Operator parameters

Schedule component pods

Allows you to configure pod scheduling fields for components so you can place them on the right nodes—for example, schedule TMM on DPUs and prevent F5 ingress, DSSM, and CWC from running on DPUs. For more information, see CNEInstance parameters

Model changes

(No model changes)

Fixed issues

2185785

CR Status set to Failed when there is a gRPC failure without recovery

Component: ingress

Symptoms:
When the Controller does not receive a response for gRPC request and all retries have been exhausted, the CR status is updated to Failed.

Conditions:
A network outage within the ControlPlane or between the ControlPlane and the DataPlane.

A ControlPlane component restarts while configuration attempts are underway. A DataPlane component restarts while attempts are underway.

Impact:
Dataplane may or may not be configured.

Fix Text Delete and reapply the affected CRs.

2200517-1

Hardware acceleration for IPv6 is not supported.

Component: FSM

Symptoms:
On the CX7 NIC, BIG-IP Next for Kubernetes hardware acceleration is not supported for IPv6 traffic. Only IPv4 traffic offloading is available, including IPv4 flow offloading, IPv4 NAT44 offloading, and ACL offloading.

Conditions:
BIG-IP Next for Kubernetes running on the CX7 NIC.

Impact:
IPv6 traffic is not optimized for acceleration.

Fix Text IPv6 offloading now is working.

Known issues

2183833-2

SIP egress CRD installation is not supported by FLO

Component: egress

Symptoms:
SIP egress CRD is not installed when installing BNK using FLO.

Conditions:
When CRD installation is done using only FLO.

Impact:
SIP egress CRD will be missing in the CRDs installed using FLO and SIP egress functionality will not be supported.

Workaround:
Install SIP egress CRD using helm.

2229789-1

DSSM upgrade failed when upgrading from BNK 2.2.0 to 2.2.1 using FLO

Component: dssm

Symptoms:
While upgrading from BNK 2.2.0 to 2.2.1 using FLO, the DSSM upgrade hook pod gets stuck in a container-creating state, preventing the DSSM pods from upgrading successfully.

Conditions:
This issue is observed when upgrading from BNK 2.2.0 to 2.2.1 using FLO.

Impact:
The DSSM DB pods are not upgraded to the latest version.

Workaround:
Before the upgrade, create a file named dssm-upgrade-cm.yaml containing the configuration for the ConfigMap in the lower version prior to performing the upgrade.

apiVersion: v1
kind: ConfigMap
metadata:
  name: f5-dssm-logs-config
data:
  .minlevel.yaml: |

Apply the dssm-upgrade-cm.yaml in the same namespace where the DSSM pods are deployed.

kubectl apply -f dssm-upgrade-cm.yaml -n <dssm pods installed name space>

2201525-2

OcNOS sending ASN 0

Component: fsm-networking

Symptoms:
BGP Neighborship fails due to OcNOS sending ASN 0 on peer open message.

Impact:
Neighborship fails to estabish.

Workaround:
To mitigate the issue:

  • Start the TMM first and then FRR.

  • Alternatively, run the command ‘no bgp XXXX’ to reconfigure the peer.

2227657

In DSSM, the timestamp for DP1 is changed when all the three DSSM containers are restarted

Component: CGNAT

Symptoms:
Restarting all three DSSM containers with pkill -15 causes new data to be lost; when the DSSM pods come back up, Redis loads the old data from the RDB file.

Conditions:
All the DSSM pods are restarted at the same time.

Impact:
The new data that are not saved in the RDB file maybe lost.

Workaround:
When deploying or upgrading the DSSM Helm chart, the administrator should set aof_enabled to true in the DSSM override file.

db:
  aof_enabled: "true"

2227705

Using the NAT CR configuration, downgrade from version 2.2.1 or later to a version earlier than 2.2.1

Component: CGNAT

Symptoms:
In the future, upgrading to version 2.2.1 or later from a version earlier than 2.2.1 without deleting the NAT CRs will cause NAT IP duplication in DSSM; the same NAT IPs may be reserved by multiple TMM pods.

Conditions:
Occurs when user,

  1. runs a 2.2.1 or later version with NAT CR configuration.

  2. downgrade to version earlier to 2.2.1 without deleting NAT CR configuration.

  3. upgrades to 2.2.1 or later version without deleting the NAT CR configuration.

Impact:
Service disruption.

Workaround:
Before downgrading to a version earlier than 2.2.1, delete the NAT CRs, then reapply them after the downgrade is complete.

2224785

During initialization the Fluentbit sidecar container can crash and restart

Component: toda_observer

Symptoms:
The crash is a classic race condition between the startup sequence and a signal handler. When Fluent Bit starts, it creates a global flb_config, whose cio field (the ChunkIO context) is initially NULL and only initialized later. If a signal triggers code (cio_stats_get) before storage initialization completes, it dereferences the NULL cio pointer, causing an illegal memory access and the OS terminates the process with a SIGSEGV or SIGABRT.

Conditions:
When SIGTERM is received during early startup.

Impact:
After restarting, the Fluent Bit container is fully functional.

Workaround:
A Fluentbit Open Source issue is created.

1926869-2

Performance may be degraded when using PVA acceleration to apps on the same chassis as TMM.

Component: FSM

Symptoms: When running BIG-IP Next for Kubernetes on a Bluefield-3 DPU, and enabling PVA Acceleration of flows, traffic destined for apps running on the host in the same chassis as the DPU with TMM may see up to 50% less throughput when compared to traffic destined for apps on other nodes in the cluster.

Conditions: PVA acceleration enabled, BIG-IP Next for Kubernetes running on Bluefield-3 DPU, Apps running on host CPU are in the same chassis as TMM.

Impact: Up to 50% degradation in throughput.

1968153-3

Traffic stats missing drop counter for trunk use cases.

Component: FSM

Symptoms: Traffic stats are not present when packet are dropped when using a trunk interface.

Conditions: The trunk does not have any interfaces to forward traffic.

Impact: Missing diagnostics.

2138129-1

Fluent-bit ARM64 image hits unsupported page size issues on ARM64 AKS cluster.

Component: Toda_fluentbit

Symptoms: When configuring a Linux kernel with the page size for 64K page size: CONFIG_ARM64_64K_PAGES=y, Fluentbit fails to start with an error “Unsupported system page size”.

Conditions: When configuring a Linux kernel with the page size for 64K page size: CONFIG_ARM64_64K_PAGES=y.

Impact: Fluentbit fails to start with an error “Unsupported system page size”.

1823977-2

Logs for TMM container is unavailable through console output when fluentbit container is enabled in TMM pod.

Component: FSM

Symptoms: When the fluentbit container is enabled for the f5-tmm pod, the f5-tmm container logs will not be outputted to the console. However, the f5-tmm container logs can still be found in the f5-toda-fluentd pod (located under “/var/log/f5”).

Conditions: Fluentbit container is enabled and running in the f5-tmm pod.

Impact: F5-tmm container logs will not be outputted through console and can only be found in the f5-toda-fluentd pod.

Workaround: The f5-tmm container logs can still be found in the f5-toda-fluentd pod (located under “/var/log/f5”).

2186317-1

Hardware-accelerated connection is not counted in DDoS Profile stats.

Component: DoS

Symptoms: Hardware-accelerated TCP/UDP connection flow packets may not be counted in DDoS Profile stats.

Conditions:

  • Hardware acceleration is enabled for context.

  • Profile DDoS is assigned to context.

  • Volumetric DDoS attack happening via accelerated connections (only TCP/UDP).

Impact: Volumetric Flood TCP/UDP DDoS attack may not be mitigated.

Workaround: Use Global DDoS to mitigate such attacks or disable hardware connection flow acceleration for context.

2046925-1

TCP throughput degradation during UDP DDoS attack with DPU hardware acceleration.

Component: DoS

Symptoms: Lower TCP throughput degradation could be observed during ongoing UDP DDoS attack on DPU platforms even when Global DDoS mitigation is configured.

Conditions:

  • Global DDoS config has TCP and UDP vectors configured.

  • DDoS hardware DPU acceleration is enabled.

  • TCP and UDP traffic is going in the same time.

Impact: Up to 30% degradation in throughput.

2186773-1

DNS Nxdomain DoS Detection & Mitigation Supported only on Global Context.

Component: DoS

Symptoms: Most DDoS Vectors are supported on both Global level & Per Context level. DNS Nxdomain DoS detection & mitigation feature is supported only on Global Context. However the Per Context DDoS CRD wrongly includes sub-section “dnsNxdomainQuery” defined, which is not supported.

Conditions: Per context DDoS CRD wrongly included sub-section “dnsNxdomainQuery”. However this configuration section is not applicable.

Impact: Including dnsNxdomainQuery vector in Per Context DDoS CRD, is misleading.

Workaround: Use Global DDoS dnsNxdomainQuery vector. Per Context level DoS mitigation is not supported for DNS Nxdomain Vector.