Bug ID 1181729: Static routes created by the F5SPKIngressGTP CR remain after the CR is deleted

Last Modified: Apr 28, 2025

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

Fixed In:
1.7

Opened: Oct 18, 2022

Severity: 2-Critical

Symptoms

Static routes created by the F5SPKIngressGTP CR remain in the TMM configuration after the CR is deleted, or the service object endpoints are scaled down.

Impact

Any new static routes added to the TMM configuration may conflict with the erroneous static routes.

Conditions

- TMM is configured with an F5SPKIngressGTP CR. - TMM creates routes pointing to the discovered service object endpoints. - The F5SPKIngressGTP CR is deleted, or the service object endpoints are scaled down. - Previously created static routes remain in TMM's configuration.

Workaround

Delete the F5SPKIngressGTP CR, scale the TMM Pod to 0, reinstall the F5SPKIngressGTP CR, then scale the TMM Pod back.

Fix Information

N/A -- There is no direct way to delete the static routes on tmm and visualize logs of their successful deletion. Will have to scale down tmm and delete the f5-ingressgtp cr.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips