Bug ID 2313345: F5-license-proxy Helm chart fails to deploy with CSI-based storage provisioners or OpenShift restricted security constraints

Last Modified: Oct 27, 2026

Affected Product(s):
BIG-IP NEXT CNF None(all modules)

Fixed In:
2.2.0

Opened: Jun 03, 2026

Severity: 2-Critical

Symptoms

When you deploy the f5-license-proxy (FLP) Helm chart in an environment that uses a CSI-based dynamic storage provisioner or in an OpenShift cluster with restricted Security Context Constraints (SCC), the following issues occure: - On OpenShift with a restricted SCC, the IPC_LOCK capability in the container securityContext prevents the vault and vault-init pods from scheduling. - Selector.matchLabels defined in the chart prevent CSI dynamic provisioners from binding volumes, leaving all PersistentVolumeClaims (PVCs) stuck in Pending. - The chart sets storageClassName: standard in all PVs and PVCs, preventing the use of a custom storage class. - The chart always creates three hostPath PersistentVolumes with no option to disable them, making CSI-based deployments unsupported. - If you upgrade the chart and change volumes.vaultDataDir, Kubernetes returns an error: spec.persistentvolumesource is immutable after creation.

Impact

Environments that use CSI-based storage or enforce OpenShift’s restricted SCC prevent deploying FLP, blocking installations entirely.

Conditions

Occurs when, - f5-license-proxy Helm chart versions earlier than 1.29.0-0.10.40 is deployed with - a Kubernetes cluster that uses a CSI-based dynamic storage provisioner (such as EBS CSI or any non-hostPath provisioner), and/or - an OpenShift cluster that enforces the restricted or restricted-v2 SCC. - Attempted to upgrade the chart while changing the volumes.vaultDataDir value.

Workaround

None

Fix Information

Fixed these issues in f5-license-proxy Helm chart (1.29.0-0.10.40) - Added storage.createPV flag (default: true) to control rendering of the three static hostPath PersistentVolumes. Set this to false to skip PV creation in CSI-based environments. - Exposed storage.storageClassName (default: "standard") and apply it uniformly to all PVs and PVCs, allowing you to specify your cluster’s storage class. - Added optional OpenShift Route support. A new flp-route.yaml template can create a Route with passthrough TLS termination (route.enabled: false by default). The Route host must match a SAN in the FLP server TLS certificate (set via FLP_HOST in setup.sh). - Removed IPC_LOCK from the vault and vault-init container securityContexts. Because disable_mlock = true is already set in vault.hcl, this capability was unnecessary and prevented scheduling under OpenShift’s restricted SCC. All containers now drop all capabilities. - Render selector.matchLabels on all three PVCs only when storage.createPV: true. Omit selectors with CSI provisioners so dynamic provisioning works correctly. Upgrade note: The immutable PV spec issue during upgrades remains an operational constraint. Chart upgrades are not supported; reinstall the chart when changing versions.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips