Bug ID 1294425: F5SPKIngressHTTP2 CR configuration fails with TLS or mTLS

Last Modified: Jun 19, 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, 1.8, 1.8.0, 1.8.2

Fixed In:
1.7.9

Opened: May 02, 2023

Severity: 2-Critical

Symptoms

HTTP2 virtual servers are not created when configured for TLS or mTLS in an F5SPKIngressHTTP2 Custom Resource.

Impact

HTTP2 traffic does not pass through the SPK.

Conditions

F5SPKIngress Custom Resource is configured for one of the following: - mTLS on the clientside - TLS on the serverside - mTLS on the serverside

Workaround

Configure the F5SPKIngressHTTP2 CR for TLS offload, with no encryption on the serverside and TLS on the clientside.

Fix Information

F5SPKIngressHTTP2 can be configured for TLS and mTLS on both clientside and serverside.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips