--- title: Turbine 26.4.3 Upgrade Instructions slug: turbine-upgrade-guide/turbine-2643-upgrade-instructions docTags: createdAt: 2026-02-04T05:23:06.520Z --- Use these instructions to upgrade your instance to Turbine 26.4.3. The instructions are organized into subsections of this document that will help you upgrade based on your installation type, whether you have an embedded or existing cluster installation. ## End of Support for Red Hat Enterprise Linux 8 (RHEL 8) RHEL 8 is no longer a supported operating system for Turbine. Beginning with Turbine 26.0.3, Kubernetes is updated to version 1.33, which does not support RHEL 8 (specifically, Linux kernel versions 4.18 and earlier). All customers running RHEL 8 must upgrade to RHEL 9 before upgrading to Turbine version 26.0.3 or greater. You can use the following to determine your host's current RHEL version: `cat /etc/redhat-release` ## Upgrade Turbine on Embedded Cluster Installations Use the following instructions to upgrade Turbine on an embedded cluster installation. ### Prerequisites - Turbine version **26.3.3** - MongoDB 8.0.24 **Important:** Swimlane recommends performing a MongoDB backup before starting this update. For more information, see [Backup and Restore on an Embedded Cluster with Snapshots](docId\:mfaXpicxqh16treIH7fE2). ### 1. Upgrade Instructions **1.1 SSH into any node in your deployment. ** **1.2 Scale down EKCO and kotsadm-rqlite** :::BlockQuote kubectl -n kurl scale deployment ekc-operator --replicas=0 kubectl -n default scale statefulset kotsadm-rqlite --replicas=0 ::: **Note:** EKCO and kotsadm-rqlite will automatically scale back up after the script in Step 1.3 completes. **1.3 Run the Turbine Platform Installer upgrade** :::BlockQuote curl -sSL https\://kurl.sh/turbine-turbine-26-4-3 | sudo bash -s ha ::: **Note:** If SELinux, a firewall, or a proxy is configured, append the following to the command: :::BlockQuote installer-spec-file=se.yaml ::: The se.yaml file is an installer patch file created as described here: https\://docs.swimlane.com/turbine-installer/overriding-installer-settings ### 2. Complete the upgrade from the UI 1. Log in to the Turbine Platform Installer dashboard: https\://\:8800 2. Go to the **Version History** tab and click **Check For Updates**. 3. In the pop-up window, click **Go to the updated version**, then click **Configure**. 4. Click **Deploy** on version **26.4.3** with the highest sequence number. 5. Once the **Application** tab shows **‘Ready’**, your upgrade is complete. ## Upgrade Turbine on Existing Cluster Installations Prerequisites: - Turbine version **26.3.3** - MongoDB **8.0.24** - Kubernetes **1.35.7** - KOTS kubectl plugin **1.130.9** - Velero **1.18.2** **Important! **Swimlane recommends that you perform a MongoDB backup before starting this update. For more information, see [Backup and Restore on an Existing Cluster with Snapshots](docId\:NQvM65bgHSOYRHs-yDTKX). **Upgrade KOTS add-on and KOTS app** ### 1. Prepare the Swimlane Turbine Installer kubectl add-on **1.1 Download the add-on for your OS** **Linux (AMD64)** :::BlockQuote curl -LO https\://github.com/replicatedhq/kots/releases/download/v1.130.9/kots\_linux\_amd64.tar.gz ::: **macOS (Apple Silicon / ARM64)** :::BlockQuote curl -LO https\://github.com/replicatedhq/kots/releases/download/v1.130.9/kots\_darwin\_arm64.tar.gz ::: **1.2 Untar the downloaded file** :::BlockQuote tar -zxf \.tar.gz ::: **1.3 Rename the kots binary to kubectl-kots** :::BlockQuote mv kots kubectl-kots ::: **1.4 Move the kubectl-kots binary into your PATH (e.g. /usr/local/bin/)** :::BlockQuote sudo mv kubectl-kots /usr/local/bin/ ::: **1.5 Run the upgrade command** :::BlockQuote kubectl kots admin-console upgrade -n \ ::: ### 2. Complete the upgrade from the UI 1. Log in to the Turbine Platform Installer dashboard: https\://\:8800 2. Go to the **Version History** tab — you will see version **26.4.3**. 3. Click **Deploy** once the preflight checks have completed. 4. Update the Elasticsearch configuration: - Configure the persistent volume size and storage class - Recommended sizes: **8GB / 16GB / 32GB** for small/medium/large environments 5. Once the **Application** tab shows **‘Ready’**, your upgrade is complete. 💡 **Note:** Replace \ with: - kots\_linux\_amd64 - kots\_darwin\_arm64 ## Upgrade Turbine on Embedded Airgap Cluster Installations ### Prerequisites - Turbine version **26.3.3** If you are not on a version that is >= 25.5.0, contact your Swimlane support representative. - MongoDB **8.0.24** - Links to the Offline Installer Package and Offline Airgap Bundle If you do not have these, contact your Swimlane support representative. **Important!** Swimlane recommends that you perform a MongoDB backup prior to starting this update. For more information, see [Backup and Restore on an Embedded Cluster with Snapshots](docId\:mfaXpicxqh16treIH7fE2). ### 1. Upgrade Instructions **1.1 Copy the latest offline installer package to each airgapped server** **1.2 Untar the offline installer package on each server** :::BlockQuote tar -xzvf turbine-26.4.3.tar.gz ::: **1.3 Run the Turbine Platform Installer update on any node in your deployment** :::BlockQuote cat install.sh | sudo bash -s airgap ha ::: Provide the absolute path for kubernetes-1.35.7.tar.gz, downloaded as part of step 2, when prompted during installation. **1.4 Run load-images script on all nodes (for HA clusters)** Once the installation is complete, if you have a multi-node (HA) cluster, the script prompts you to run an additional command on every node. Run this script on node swimlane-2 to load required images before proceeding: :::BlockQuote cat ./tasks.sh | sudo bash -s load-images ::: You will be prompted: :::BlockQuote Have images been loaded on node swimlane-2? (Y/n) ::: Run the following on nodes two (2) and three (3) before proceeding to run the command on node one (1): :::BlockQuote cat ./tasks.sh | sudo bash -s load-images ::: This command can be run simultaneously on nodes 2 and 3. Once the load-images script completes, press **Enter** on node 1 and then upload the airgap bundle to the SPI dashboard. **1.5 Complete the upgrade** When the upgrade script completes, press **Enter** on node 1 and then upload the airgap bundle to the SPI dashboard. Log in to the Turbine Platform Installer dashboard: https\://\:8800 Go to the **Version History** tab and click **Upload a new version**, then browse to the turbine-26.4.3.airgap file and click **Upload**. The sequence number “\_XXX” of the airgap file may be higher than shown if a new sequence has been published. Once the upload of the airgap completes, refresh the page or switch tabs to see the status of the new file extraction. Go back to the **Version History** tab and click **Deploy** on the new 26.4.3 version at the top of the versions list. Once the **Application** tab shows **‘Ready’**, your upgrade is complete. ## Upgrade Turbine on Existing Airgap Cluster Installations ### Prerequisites - Turbine version **26.3.3** - MongoDB **8.0.24** - Kubernetes **1.35.7** - KOTS kubectl plugin **1.130.9** - Velero **1.18.2** - Turbine **26.4.3 airgap bundle** from Swimlane Contact your Swimlane support representative if you do not have a download link for the airgap bundle. **Important!** Swimlane recommends that you perform a MongoDB backup before starting this update. For more information, see [Backup and Restore on an Existing Cluster with Snapshots](docId\:NQvM65bgHSOYRHs-yDTKX). ### 1. Upgrade KOTS plugin and KOTS app **1.1 Download the latest SPI Kubectl Add-on** See kots documentation for how to do so. A versioned link will look like this (Linux AMD64): :::BlockQuote curl -LO https\://github.com/replicatedhq/kots/releases/download/v1.130.9/kots\_linux\_amd64.tar.gz ::: **1.2 Download the latest SPI offline package** :::BlockQuote curl -L https\://get.swimlane.io/existing-cluster/install/offline-package -o kotsadm.tar.gz ::: **1.3 Copy the SPI Kubectl Add-on and SPI offline package to your jumpbox** :::BlockQuote scp kots\_\.tar.gz user@\:/tmp/kots\_\.tar.gz scp kotsadm.tar.gz user@\:/tmp/kotsadm.tar.gz ::: **1.4 Untar the SPI Kubectl Add-on** :::BlockQuote tar -zxvf kots\_\.tar.gz ::: **1.5 Rename or remove the original kubectl-kots file** :::BlockQuote rm /usr/local/bin/kubectl-kots ::: **1.6 Rename and move the latest SPI Kubectl Add-on file to /usr/local/bin/** :::BlockQuote mv kots kubectl-kots sudo mv kubectl-kots /usr/local/bin/ ::: **1.7 Push the SPI (kotsadm) images to your registry** :::BlockQuote kubectl kots admin-console push-images kotsadm.tar.gz \/\ \ --registry-username \ --registry-password \ ::: **1.8 Upgrade the Swimlane Platform Installer (SPI)** :::BlockQuote kubectl kots admin-console upgrade \ --kotsadm-registry \/\ \ --registry-username \ \ --registry-password \ \ -n \ ::: When the SPI upgrade is complete, upload the Turbine airgap bundle to the SPI dashboard. ### 2. Complete the upgrade from the UI 1. Log in to the Swimlane Platform Installer dashboard: https\://\:8800 2. Go to the **Version History** tab and click **Upload a new version**, then browse to the turbine-26.4.3.airgap file and click **Upload**. 3. The sequence number “\_xxx” of the airgap file may be higher than shown if a new sequence has been published. 4. Once the upload completes, refresh the page or switch tabs to see the status of the file extraction. 5. Go to the **Version History** tab — you will see version **26.4.3**, then click **Configure**. 6. Click **Deploy** on the new 26.4.3 version at the top of the versions list. 7. Once the **Application** tab shows **‘Ready’**, your upgrade is complete. ### General Note If you face any issues downloading Kubernetes: Download and copy kubernetes-1.35.7.tar.gz on each server. The file can be downloaded on the jump server using: :::BlockQuote curl -LO https\://kurl.sh/bundle/version/v2026.10.07-0/turbine-stable-multitenant/packages/kubernetes-1.35.7.tar.gz ::: ## Known Issue - **Application Field Limit Stays at 500 After Upgrade** — After you upgrade to 26.4.3, tenants whose largest application or applet already has 500 or more search-indexed fields are raised automatically to peak + 100. If a tenant still shows **500** and Application Builder blocks new indexed fields, a Super Admin can open **Tenant Settings > System** and raise **Application Field Limit**, or you can restart the **swimlane-tasks** pod so the check runs again. - **Tasks and API Pods Do Not Reach Running State** — After deploying or upgrading Turbine On-Prem 26.2.2, the swimlane-tasks and swimlane-api pods can remain stuck in init while waiting for the swimlane-tenant service. This can occur even when swimlane-tenant pods report healthy liveness and readiness checks but the service is not yet accepting requests. The issue is sporadic and does not affect every environment. **Workaround:** Restart the swimlane-tenant deployment so the Kubernetes service routes traffic to the new pods; swimlane-tasks and swimlane-api should then start normally.