Bug ID 1602085: Data in configmap used for persistence by f5ingress can become temporarily stale after tmm scaling events

Last Modified: Oct 19, 2025

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

Known Affected Versions:
1.7.9, 1.7.10, 1.7.11

Opened: Jun 27, 2024

Severity: 3-Major

Symptoms

The configmap is used by f5ingress controller to persist TMM specific config assignments like selfIP, snatIP and more. The configmap data could be out of sync with the state of the system.

Impact

If f5ingress is restarted while persistmap is stale, duplication of selfips and snat routes can occur.

Conditions

Multiple TMM pod scaling events are occurring in quick succession, such that their processing overlaps. And then f5ingress is restarted before it is able to get persistmap back in sync.

Workaround

The Product Engineering (PE) team and Professional Services (PS) team are working on enhancing Kubernetes cron job script to identify error conditions involving duplicate config, which could help recover from bad state. Please contact F5 for cron job script.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips