Install F5 License Proxy using the setup utilityΒΆ
F5 License Proxy (FLP) is a lightweight service that automates and centralizes the licensing of F5 BIG-IP Virtual Editions. Instead of handling licensing manually on each device, FLP acts as a proxy between your BIG-IP instances and F5βs licensing servers.
Note
Before installing f5-license-proxy, verify that no Persistent Volume Claims (PVCs) from a previous f5-license-proxy installation remain. If any are present, delete them manually before proceeding.
Follow the steps below based on your deployment environment:
hostPath (local storage): The setup script must be run directly on the Kubernetes worker node where FLP is scheduled β not from a jumphost. Directory permissions are set locally on the machine running the script; if executed remotely, they will not apply to the actual node, and the PostgreSQL and Vault containers will fail to start with
Permission denied.OpenShift (OCP): During installation, always select
Yfor CSI-based storage and provide the appropriate StorageClass name. On OCP, CSI drivers handle volume ownership automatically, the permission step is skipped entirely, and the script can be run safely from a jumphost.
Grant execute permissions to setup file.
chmod +x flp-setup-1.29.0-0.10.5/setup-1.29.0-0.10.5.sh
Run the setup file.
sudo KUBECONFIG=$HOME/.kube/config ./flp-setup-1.29.0-0.10.35/setup-1.29.0-0.10.35.sh
Example output
π Running prerequisite checksβ¦ β Ubuntu 24.04 detected β OK β tar version 1.35 meets minimum requirement 1.29. β openssl version 3.0.13 meets minimum requirement 1.1.1. β curl version 8.5.0 meets minimum requirement 7.58.0. β helm version 3.18.4 meets minimum requirement 3.17.1. β kubectl version 1.33 meets requirements. prerequisite checks successful ```
Enter Kubernetes namespace for install when prompted.
Enter Kubernetes namespace to install into [default]:
Example output
β Using namespace: default π Running setup configuration...
Enter the JWT token when prompted.
Enter JWT Token: <<JWT Token>>
Enter the image repository path when prompted.
Enter the image repository:<<repo path>>
Enter the image pull secret name when prompted.
Enter the image pull secret name [far-secret]:
Example output
β Image pull secret 'far-secret' found.
Answer whether or not you are using CSI-based storage when prompted.
Are you using CSI-based storage (e.g., NetApp Trident, EBS CSI)? (Y/N)[N]: Y (Note: Press Enter for default host path storage)
Enter your StorageClass name when prompted.
Enter your StorageClass name (e.g., trident-csi): managed-nfs-storage
Example output
β CSI storage configured: createPV=false, storageClassName=managed-nfs-storage
Answer whether or not to create an OpenShift route in front of FLP when prompted.
Create an OpenShift Route in front of FLP? (Y/N)[N]: Y (Note: Press Enter to skip β only applicable on OpenShift clusters)
Enter Route hostname when prompted.
Enter Route hostname (flp.apps.<your-cluster-domain>): flp.apps.ocp7.pd.example.com
Example output
β OpenShift Route will be created for host: flp.apps.ocp7.pd.example.com FLP server cert SAN will be regenerated to include flp.apps.ocp7.pd.example.com
Enter the full Helm chart path when prompted.
```shell
Enter the full HELM Chart.yaml path: /root/f5-license-proxy
```
*Example output*
```shell
β
Valid f5-license-proxy chart found at: /root/f5-license-proxy
```
Press Enter when prompted to set up a proxy. If you choose Y to set up a proxy, follow Forward Proxy Utility.
```shell
Do you want to set up a proxy? (Y/N)[N]:
```
*Example output*
```shell
Skipping proxy setup.
```
Press Enter when prompted to restore FLP root certificates.
```shell
Do you want to restore FLP root certificates? (Y/N)[N]:
```
*Example output*
```shell
Starting MTLS execution - creating root CA
Starting MTLS execution - creating server cert
Starting vault execution - creating server cert
Environment preparation successful
Create the secret for flp-jwt-secret flp-mtls-secret postgresql-mtls-secret vault-ssl-secret
Secret creation successful
Creating backup of FLP root certificates
```
Set up an encryption password for the FLP root certificates backup.
:::{important}
Retaining a copy of the root certificate is mandatory as it will be required for any future restoration of the FLP. Restoring the FLP with the same root certificate is essential to preserve the trust relationship between the FLP and the BNK/CNE cluster. Using a different root certificate during restoration may disrupt the trust relationship and cause communication issues.
:::
```shell
Encryption password for FLP root certificates backup:
```
Re-enter the encryption password for the FLP root certificates backup.
```shell
Reenter encryption password for FLP root certificates backup:
```
*Example output*
```shell
Passwords accepted.
Creating backup bundle backup.20250627-083720.tgz...
Encrypting backup bundle...
Backup bundle created at /root/.flp_spk_backup/backup.20250627-083720.tgz.enc
```
Install/upgrade the Helm version.
helm upgrade --install f5-license-proxy /root/f5-license-proxy --timeout 600s --namespace flp-ns --set flp.image.repository=devrepo.f5.com/images --set vault.image.repository=devrepo.f5.com/images --set vaultInit.image.repository=devrepo.f5.com/images --set postgresql.image.repository=devrepo.f5.com/images --set storage.createPV=false --set storage.storageClassName=managed-nfs-storage --set route.enabled=true --set route.host=flp.apps.ocp7.pd.f5net.com
Example output
Release "f5-license-proxy" does not exist. Installing it now. NAME: f5-license-proxy LAST DEPLOYED: Mon Aug 17 09:56:58 2026 NAMESPACE: default STATUS: deployed REVISION: 1 TEST SUITE: None NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION f5-license-proxy default 1 2026-08-17 09:56:58.013099751 +0530 IST deployed f5-license-proxy-1.29.0-0.10.40 1.29.0-0.10.40 f5-spk-crds-common default 1 2026-08-15 23:08:58.454372127 +0530 IST deployed f5-spk-crds-common-14.19.4-0.1.58 v14.19.4-0.1.58 f5-spk-crds-service-proxy default 1 2026-08-15 23:08:54.20628542 +0530 IST deployed f5-spk-crds-service-proxy-14.19.4-0.1.58 v14.19.4-0.1.58 Install/Upgrade the helm successful Cleaning up stale hostPath data from previous installations... β Stale data cleaned. Fixing vault directory permissions for vault user (uid=100, gid=1000)... β Vault directory permissions fixed. Fixing postgresql directory permissions for postgresql user (uid=1001, gid=1001)... β PostgreSQL directory permissions fixed.
You must securely store the FLP root certificate backup bundle created at
$HOME/.flp_spk_backup/backup.20250627-083720.tgz.encto ensure it is available when needed.
Enable a proxyΒΆ
Run the setup reconfiguration.
./flp-setup-1.29.0-0.10.5/setup-1.29.0-0.10.5.sh --reconfigExample output
π Running setup reconfiguration...
Enter the Helm Chart.yaml path when prompted.
Enter the full HELM Chart.yaml path: /root/f5-license-proxy
Example output
β Valid f5-license-proxy chart found at: /root/f5-license-proxy
Answer
Ywhen prompted to set up a proxy.Step 3: Do you want to set up a proxy? (Y/N)[N]: y
Enter the proxy host name when prompted.
Enter Proxy Host: <<enter proxy host name>>
Enter the proxy port when prompted.
Enter Proxy Port: <<enter Port>>
Example output
Proxy Host=cpcl-proxy.pdhyd.f5net.com, Proxy Port=3001
Enter the proxy protocol when prompted.
Enter Proxy Protocol (http/https)[http]: https Proxy ca bundle incase of https:
Press Enter then CTRL+d to finish.
Answer
Ywhen prompted to enable proxy authentication.Step 8: Enable proxy authentication? (Y/N)[N]: y
Enter the proxy username when prompted.
Enter Proxy Username: example-user
Enter the proxy password when prompted.
Enter Proxy Password:
Example output
π Validating proxy: cpcl-proxy.pdhyd.f5net.com:3001... β Proxy validation successful. Create the secret for flp-secret flp-ssl-secret Secret creation successful Install/Upgrade the helm helm upgrade --install f5-license-proxy /root/f5-license-proxy --timeout 600s --namespace default --set flp.isProxyEnabled=true --set flp.isProxyTlsEnabled=true --set flp.isProxyAuthEnabled=true Release "f5-license-proxy" has been upgraded. Happy Helming! NAME: f5-license-proxy LAST DEPLOYED: Thu Jul 3 07:03:51 2025 NAMESPACE: default STATUS: deployed REVISION: 2 TEST SUITE: None NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION f5-license-proxy default 2 2025-07-03 07:03:51.007433306 +0000 UTC deployed f5-license-proxy-1.29.0-0.10.5 1.29.0-0.10.5 Install/Upgrade the helm successful