Release 17.0.0
Released: 2026-10-08
This version of base is only compatible with application version 26.5 or higher and allows in-place upgrades from base version 15 or higher.
Shell access now requires a one-time code from Forward Networks support. To open a Linux shell from the TUI:
- Select Troubleshooting > Exit to Shell, then select Request.
- Send the challenge shown on the screen to Forward Networks support. The Copy Challenge button copies it.
- Type the 8-digit code that support gives you, then select Exit to Shell.
The shell stays open for up to 8 hours and closes when you leave it.
Security
- Upgraded several Linux packages and addressed 217 vulnerabilities.
- Exit to Shell requires a one-time code from Forward Networks support. After five wrong codes, unlock attempts are blocked for 15 minutes, and challenge requests are limited to 20 per hour. Changing the system clock doesn't reset these limits.
- The TUI upload server now accepts only valid Forward app packages and rejects all other files.
- The HA registry containers now run with minimal privileges, and the registry gateway runs as a non-root user.
Fwd-tui
- Adds an MTU field to Node > Networking and to the
hostCLI. The change applies right away without a reboot. - The diagnostics bundle now records the eth0 MTU.
Bug Fixes
- Resolved an issue where the registry gateway could stay out of service for several minutes after a restart while the registries synced.
- Resolved an issue where kernel messages overwrote the setup screen on the VM console.
- Resolved issues with changing a node's IP address, where k0s could stay disabled after the change and the TUI could crash.
Upgrade from previous versions
It is strongly recommended that a support engineer from Forward Networks is present when doing the upgrade to avoid mistakes that can impact the deployment.
Check the base version using the below command and make sure it is at least 15.0.0. Direct upgrade from previous base versions is not supported.
BaseVersion: cat /opt/forward/updates/system/original-version
This upgrade takes about 5 minutes per node. During the base upgrade, the nodes will be rebooted and the Forward application will be unavailable for some of that time.
If you are upgrading from base 16.4 or lower, redeploy the Forward Enterprise application after the base upgrade completes. Follow the steps in Deploy Forward Enterprise application.
Upgrade from base version v16.4.0 or higher
If the cluster node has internet access, the upgrade package can be downloaded directly on the VM. If the VM does not have internet access, the upgrade file must be downloaded locally to your machine and then uploaded to the primary node.
- If the VM does not have internet access, download forward-base-update-17.0.0.tar.gz to your local machine before continuing.
- Log in to one of the primary nodes over SSH or the VM console
- Select Cluster > Upgrade base from the TUI, then choose Upload New Package
- Choose one of the following upload methods:
- HTTPS (Browser): opens a temporary upload service at
https://<node-ip>:30000where the package can be uploaded through a browser - SSH (SFTP): opens a temporary SFTP service on port 30000 for transferring the package via SCP/SFTP. Connect as
the
forwarduser with the one-time password shown by the TUI:scp -P 30000 forward-base-update-17.0.0.tar.gz forward@<Primary_Node_IP>:~/ - Download from URL: enter the URL of the base upgrade tar file, then click Download
- HTTPS (Browser): opens a temporary upload service at
- Select the upgrade file uploaded in the previous step, then select Start Upgrade to start the base upgrade
- Confirm the upgrade when prompted to initiate the process
- Wait for completion:
- For a multi-node cluster, fwdtui handles the upgrade for all nodes automatically. It copies the upgrade file to every node and upgrades each of them.
- The upgrade reboots the primary node. Once it becomes available again, SSH back into it
- Select Cluster > Upgrade base from the TUI, then choose Resume Upgrade
- Once the upgrade completes successfully, select Close to close the upgrade logs view
Upgrade from base version v16.3.0 or lower
Upgrade base OS
Ensure that TCP port 30000 is open for inbound traffic to the cluster nodes. This port is required for file upload and download operations. See the network requirements for the full list of required ports.
- On every node (1 node at a time)
- Download forward-base-update-17.0.0.tar.gz and forward-base-update-17.0.0.sha256 files
- Verify the update file integrity using the command below:
sha256sum --check forward-base-update-17.0.0.sha256
- Extract contents of the update file:
tar -zxf forward-base-update-17.0.0.tar.gz
- Navigate into the forward-base-update-17.0.0 folder:
cd forward-base-update-17.0.0
- Start the base upgrade by executing the command below:
./run_update.sh
- Wait for completion.
- After script has finished rebooting the node and node becomes available again, ssh to the node and run the script:cd forward-base-update-17.0.0./run_update.sh
- After script has finished rebooting the node and node becomes available again, ssh to the node and run the script:
- Run
base_updates_utils DESCRIBEfrom the command line, and confirm that you are on base version17.0.0. - The forward-base-update-17.0.0.tar.gz file and the corresponding unzipped directory can be deleted at this time:
rm -rf forward-base-update-17.0.0*
Upgrade cluster components
This upgrade takes about 5 minutes and during this upgrade the Forward application may be unavailable for some of that time.
-
On one of the primary nodes
-
Launch the fwd-cluster utility by running the following command
fwd-cluster -
The utility will detect any pending k0s updates and prompt you to confirm the upgrade. When prompted, enter y and press Enter to proceed with the upgrade.
K0S Update found, do you want to apply it now? [y/n]: y -
Once the upgrade completes successfully, exit the fwd-cluster utility
-
Deploy Forward Enterprise application
This step is required when upgrading from base 16.4 or lower.
- Log in to one of the primary nodes where the application package is present
- Select Forward Enterprise > Install/Upgrade from the TUI
- Select the package file, then choose Deploy to push the Forward Enterprise application images to the new registry
- Select Close once the application is redeployed