Bug ID 1856493: Multiple SNAT pool Custom Resources (CRs) are not supported in a single namespace.

Last Modified: Nov 29, 2025

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

Known Affected Versions:
1.4.0

Opened: Mar 17, 2025

Severity: 2-Critical

Symptoms

The routes present in the SNAT pool Custom Resources are not reflecting in the routing container of the TMM pod.

Impact

Only the latest SNAT pool Custom Resource routes are reflecting in the routing container of the TMM pod. The earlier SNAT pool Custom Resource routes are overridden.

Conditions

The issue occurs while configuring multiple SNAT pool CRs followed by one of the scenarios mentioned here: • When a new TMM instance starts. • When an existing TMM restarts.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips