Bug ID 1772861: Deploying CNF v1.4.0 on Kubernetes v1.30 and later fails.

Last Modified: Nov 29, 2025

Affected Product(s):
BIG_IP_NEXT(CNF) CNF(all modules)

Fixed In:
1.4.0

Opened: Dec 13, 2024

Severity: 1-Blocking

Symptoms

Attempting to deploy CNF v.1.4.0 on Kubernetes v.1.30 and later fails.

Impact

The deployment fails.

Conditions

Attempting to deploy CNF v.1.4.0 on Kubernetes v1.30 and later.

Workaround

Note: This workaround requires switching to a non-production environment and may impact performance. Add the following TMM environment variables to the values override file: - name: TMM_MAPRES_HALT value: "false" - name: PAL_CPU_SET value: "<cpuset for tmm to use>" The first variable is used to switch to a non-production environment. The cpuset argument can be a subset of the cpuset provided to the TMM container.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips