Last Modified: Dec 04, 2024
Affected Product(s):
BIG_IP_NEXT(SPK) SPK
Fixed In:
1.9.2
Opened: May 06, 2024 Severity: 2-Critical
When an F5SPKIngressHTTP2 Custom Resource instance is configured for a service, if the deployment(s) for that service are scaled down, the configuration remains in the f5-tmm. Additionally, if the f5-tmm is scaled up, the configuration is not applied to new f5-tmm pods.
In the application deployment scale-down scenario, the f5-tmm will attempt to send traffic to deployments that no longer exist, and static routes will remain in the f5-tmm. In the f5-tmm scale-up scenario, only the f5-tmm pods present at the time of F5SPKIngressHTTP2 CR creation will handle traffic.
- F5SPKIngressHTTP2 Custom Resource is configured to use one or more services. - The deployment(s) in one or more services are scaled down or - The f5-tmm deployment(s) are scaled up.
Options: 1. Remove the F5SPKIngressHTTP2 CR prior to scaling down the deployment(s) and then reapply the CR once completed 2. In case the deployment has already been scaled down, scale the f5-tmm deployment to zero and then increase it again. 3. When you want to scale-up f5-tmm, scale it up as needed, and then remove and reapply the F5SPKIngressHTTP2 CR(s).
The SPK Handler for F5SPKIngressHTTP2 CR now properly manages the deployments scale-down and the scale-up of f5-tmm.