Last Modified: Nov 29, 2025
Affected Product(s):
BIG_IP_NEXT(CNF) CNF
Known Affected Versions:
1.3.1, 1.3.2, 1.3.3
Fixed In:
1.4.0
Opened: Oct 15, 2024 Severity: 1-Blocking
When the node hosting the f5ingress pod goes down or fails, the f5ingress pod encounters an error and fails to redeploy on another node.
New configurations will not be applied to existing pods. Additionally, existing configurations will not be applied to newly deployed pods or pods that are restarted or scaled up.
The node hosting the f5ingress pod goes down. In the Kubernetes manager logs, the following message is observed for the f5ingress pod: ".env: duplicate entries for key [name=\"GRPC_SERVICE_NAME\"]"
Edit the f5ingress deployment and remove the duplicate entry for GRPC_SERVICE_NAME in the 'env' section of the f5ingress container.
Remove gRPC service name field from extraEnvs in TMM values file.