Last Modified: Aug 30, 2024
Affected Product(s):
BIG_IP_NEXT(SPK) SPK
Known Affected Versions:
1.7, 1.7.1
Fixed In:
1.9.2, 1.7.2
Opened: Mar 30, 2023 Severity: 3-Major
F5ingress controller fails to configure TMM with virtual server and pool members after an F5SPKIngressTCP CR that does not have a service port is deployed.
When a F5SPKIngressTCP CR that does not have a service port is present and an application Pod is scaled up from zero, TMM does not get configured with virtual servers for already deployed valid CRs. If an application Pod is scaled up from non-zero replicas, pool members to existing virtual server for valid CRs do not get updated.
When a single F5SPKIngressTCP CR that does not have a service port is deployed along with other CRs that do have service ports, TMM fails to configure for any subsequent application Pod scale events.
Delete all F5SPKIngressTCP CRs that refer to non-existing service ports and then restart the f5ingress controller Pod.
Now, TMM continues to be configured for CRs that have service ports even if there are CRs that do not have service ports.