Last Modified: Oct 19, 2025
Affected Product(s):
BIG_IP_NEXT(SPK) SPK
Known Affected Versions:
1.7.9, 1.7.10, 1.7.11
Opened: Sep 12, 2024 Severity: 3-Major
The ConfigMap utilized for persistence by the control plane (F5ingress Controller) does not have self IP mappings.
A simultaneous TMM scale-down and scale-up event may occur when one pod is in the deletion state while another pod is starting up. During this process, the control plane may attempt to assign self IPs to the new TMMs but could accidentally reuse IPs already assigned to other TMMs, leading to traffic disruptions
A simultaneous TMM scale-down and scale-up event occurs when one pod is in the deletion state while another pod is starting up.
Update the ConfigMap to match the self IP assignments on the TMMs and restart the F5ingress pod. Note that F5 has provided a cron script to detect such issues in user environments and take preventive action when possible.
None