Last Modified: May 21, 2026
Affected Product(s):
BIG_IP_NEXT(CNF) CNF
Fixed In:
1.3.1
Opened: Apr 03, 2024 Severity: 2-Critical
When a TMM pod is deleted, there is a chance that some Snatpool addresses assigned to a pod will be forgotten by F5ingress while doing the conversion from pod uuid to ip. This can occur if the TMM pod is already deleted and so the conversion mapping for that pod is not accessible. This results in F5ingress thinking it has less Snatpool addresses than the Snatpool CR says it should.
Some TMMs won't get Snatpool config even though there is sufficient Snatpool config to assign to them. This can negatively effect traffic passage.
1. Snatpool CR is applied 2. TMM pod is deleted, via any of the following: scale down, helm upgrade, direct pod deletion.
Restart F5ingress. This causes F5ingress to reload the Snatpool CR into memory and get back the Snatpool config it lost.
F5ingress will compare assigned addresses to the Snatpool CR's addresses when computing the available Snatpool addresses. This way, if any addresses are lost in the uuid to ip conversion due to pod deletion, they will be reacquired.