Bug ID 2230849: Helm installation fails when namespace length causes pre-install hook Job name to exceed Kubernetes 63-character limit

Last Modified: Oct 16, 2026

Affected Product(s):
BIG_IP_NEXT(BNK) BNK(all modules)

Fixed In:
2.3.3, 2.2.4

Opened: Mar 09, 2026

Severity: 3-Major

Symptoms

Installation of the f5ingress Helm chart may fail during the pre-install hook phase when deployed into namespaces with lengthy names. During installation, Helm generates a pre-install hook Job whose name includes the namespace value. If the namespace is too long, the resulting Job name exceeds the Kubernetes 63-character label limit, causing the Job creation to fail and terminating the Helm installation. The installation error may appear similar to: INSTALLATION FAILED: failed pre-install: warning: Hook pre-install ... failed: Job.batch "...prehook-job-<namespace>" is invalid: spec.template.labels: Invalid value: "...": must be no more than 63 characters

Impact

The Helm installation fails, preventing deployment of the f5ingress components in the affected namespace.

Conditions

This issue occurs when: - The f5ingress Helm chart is installed - The deployment namespace name is longer than approximately 36 characters - The pre-install hook Job name is generated using the namespace value - The resulting Job name exceeds Kubernetes’ 63-character limit for label values

Workaround

Deploy the Helm chart in a namespace whose name length allows the generated Job name to remain within the Kubernetes 63-character limit.

Fix Information

Updated the Helm chart template for the pre-install hook Job name to use a truncated and hashed version of the namespace, instead of appending the full namespace value. The hash prevents name collisions between different long namespaces that share the same truncated prefix, ensuring the generated Job name always stays within the Kubernetes 63-character label limit.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips