Bug ID 1235861: Static routes created by the F5SPKIngressHTTP2 CR remain after the CR is deleted

Last Modified: Apr 28, 2025

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

Known Affected Versions:
1.7, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.7.7, 1.7.8

Fixed In:
1.8, 1.7.9

Opened: Feb 08, 2023

Severity: 3-Major

Symptoms

Static routes created by the F5SPKIngressHTTP2 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 routes to pool members for F5SPKIngressHTTP2 CR. After deleting the CR routes are not removed

Workaround

After deleting the CR scale TMM pod to 0 and scale it back to 1

Fix Information

HTTP2 configuration is deleted after F5SPKIngressHTTP2 CR deleted.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips