Install the F5 License Proxy using setup utilityΒΆ
Grant execute permissions to setup file.
chmod +x flp-setup-1.29.0-0.10.12/setup-1.29.0-0.10.12.sh
Run the setup file.
./flp-setup-1.29.0-0.10.12/setup-1.29.0-0.10.12.sh
Sample Output:
π Running prerequisite checks... β Ubuntu 18.04 detected β OK β tar version 1.29 meets minimum requirement 1.29. β openssl version 1.1.1 meets minimum requirement 1.1.1. β curl version 7.58.0 meets minimum requirement 7.58.0. β helm version 3.18.3 meets minimum requirement 3.17.1. β kubectl version 1.32 meets requirements. prerequisite checks successful π 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 full HELM Chart path when prompted.
Enter the full HELM Chart.yaml path: <<helm path>>
Sample Output:
β Valid f5-license-proxy chart found at: /root/f5-license-proxy
Press Enter when prompted to setup a proxy. If you choose Y to setup a proxy, follow Configure a proxy using setup utility.
Do you want to set up a proxy? (Y/N)[N]:
Sample Output:
Skipping proxy setup.
Press Enter when prompted to restore FLP root certificates.
Do you want to restore FLP root certificates? (Y/N)[N]:
Sample Output:
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 a Encryption password for 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.
Encryption password for FLP root certificates backup:
Re-enter the Encryption password for FLP root certificates backup.
Reenter encryption password for FLP root certificates backup:
Sample Output:
Passwords accepted. Creating backup bundle backup.20250627-083720.tgz... Encrypting backup bundle... Backup bundle created at $HOME/.flp_spk_backup/backup.20250627-083720.tgz.enc Install/Upgrade the helm helm upgrade --install f5-license-proxy /root/f5-license-proxy --timeout 600s --namespace default --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 Release "f5-license-proxy" does not exist. Installing it now. NAME: f5-license-proxy LAST DEPLOYED: Fri Jun 27 08:37:20 2025 NAMESPACE: default STATUS: deployed REVISION: 1 TEST SUITE: None NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION f5-license-proxy default 1 2025-06-27 08:37:20.475610819 +0000 UTC deployed f5-license-proxy-1.29.0-0.10.12 1.29.0-0.10.12 Install/Upgrade the helm successful
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.