Bug ID 1325233: F5SPKIngressHTTP2 CR does not configure virtual servers

Last Modified: Jun 19, 2025

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

Known Affected Versions:
1.8, 1.8.0, 1.8.2

Opened: Jul 26, 2023

Severity: 2-Critical

Symptoms

F5SPKIngressHTTP2 Custom Resource may not configure virtual servers under some conditions.

Impact

HTTP traffic does not ingress into the SPK Application Pods.

Conditions

An F5SPKIngressHTTP2 Custom Resource is configured in the cluster before an F5SPKVlan Custom Resource with F5SPKVlan CR boolean "internal" set to true. OR All CRs are configured before installing/restarting F5 Ingress Controller, including F5SPKIngressHTTP2 and F5SPKVlan with boolean "internal" set to true.

Workaround

Delete and re-create the F5SPKIngressHTTP2 CR after F5SPKVlan CR with boolean "internal" set to true is configured.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips