Last Modified: Oct 16, 2026
Affected Product(s):
BIG_IP_NEXT(BNK) BNK
Fixed In:
2.4.0, 2.3.3, 2.2.4
Opened: Apr 25, 2026 Severity: 3-Major
In release 2.2.0, installers had to manually configure resource limits for the Fluent Bit sidecar in the f5-downloader and f5-toda-fluentd pods in the Helm charts during installation. The cluster enforces the rq-f5-cor-cgn ResourceQuota, which requires explicit CPU and memory limits for all containers.
Pod creation failed with quota errors
Unable to deploy the f5-downloader and f5-toda-fluentd pods in Kubernetes because required resources were missing: the fluentbit sidecar container definition in f5-downloader and the fix-perms and fix-home-perms init container definitions in f5-toda-fluentd.
None
Starting with 2.2.x, the Helm charts configure CPU and memory limits by default (including for f5-downloader’s Fluent Bit sidecar and f5-toda-fluentd init containers), removing the need for manual settings.