--- title: Turbine 23.5.1 Upgrade Instructions slug: turbine-upgrade-guide/turbine-2351-upgrade-instructions docTags: createdAt: 2025-12-01T07:46:32.415Z --- Use these upgrade instructions to upgrade your instance of Turbine 23.x. The instructions are organized by subsections of this document that will help you upgrade by specific installation type, whether you have an embedded or existing cluster installation. ## Upgrade Turbine on Embedded Cluster Installations Use the following instructions to upgrade this version of Swimlane on an embedded cluster installation. Prerequisites: - Turbine version 23.2.x+ - MongoDB 5.0.14 **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. ### Upgrade Instructions 1. SSH into any node in your deployment. 2. Scale down EKCO and kotsadm-rqlite. :::BlockQuote{indent="1"} kubectl scale statefulsets kotsadm-rqlite --replicas=0 -n default ::: :::BlockQuote{indent="1"} kubectl scale deployment ekc-operator --replicas=0 -n kurl ::: 3. Execute the following command to begin the Turbine Platform Installer component upgrade: :::BlockQuote{indent="1"} $ curl -sSL https\://kurl.sh/turbine-turbine-23-5-1 | sudo bash -s ha ::: 4. After the install script has completed, log in to the Turbine Platform Installer dashboard (https\://\:8800). 5. Go to the Version History tab and click Check For Updates. 6. A pop-up window appears, click **Go to updated version** and click configure. 7. Scroll down to Swimlane Logging Level and change default, warn, to info and then save. 8. Click **Deploy** on the new 23.5.1 version with the highest sequence number at the top of the versions list. 9. Once the Application tab shows ‘Ready’ your upgrade is complete. ## Upgrade Turbine on Existing Cluster Installations ## Prerequisites: - Turbine version 23.2.x+ - MongoDB 5.0.23 - Kubernetes 1.22-1.27 - KOTS kubectl plugin 1.105.1 - Velero 1.10.x **Important! **Swimlane recommends that you perform a MongoDB backup prior to starting this update. For more information, see Backup and Restore on an Existing Cluster with Snapshots. ### Upgrade Instructions 1. SSH into any node in your deployment. 1. Download the Swimlane Turbine Installer kubectl add-on for the OS version where you run kubectl commands from: Linux: https\://get.swimlane.io/turbine/existing-cluster/install/linux OSX: https\://get.swimlane.io/turbine/existing-cluster/install/osx 2. Untar the file: :::BlockQuote{indent="2"} tar zxf kots\_\.tar.gz ::: :::Paragraph{listStyleType="decimal" listStart="3" listRestartPolite="3" indent="2"} Rename the kots binary to kubectl-kots: ::: :::BlockQuote{indent="2"} mv kots kubectl-kots ::: :::Paragraph{listStyleType="decimal" listStart="4" listRestartPolite="4" indent="2"} Move the kubectl-kots binary into your PATH so that it can be recognized by kubectl (e.g. /usr/local/bin/) ::: :::BlockQuote{indent="2"} mv kubectl-kots /usr/local/bin/ ::: 2. Run the upgrade command: :::BlockQuote{indent="1"} kubectl kots admin-console upgrade -n \ ::: 3. Download Velero 1.10.2 for your OS version: :::Paragraph{indent="1"} https\://github.com/vmware-tanzu/velero/releases/tag/v1.10.2 ::: 4. Untar the file and then change directory (cd) into the uncompressed directory: :::BlockQuote{indent="1"} $ tar -zxf \.tar.gz ::: :::BlockQuote{indent="1"} $ cd \ ::: 5. Update Velero custom resource definitions: :::BlockQuote{indent="1"} $ ./velero install --crds-only --dry-run -o yaml | kubectl apply -f - ::: 6. Update the images Velero and Restic use to 1.10.2 :::BlockQuote{indent="1"} $ kubectl set image daemonset/restic restic=velero/velero\:v1.10.2 --namespace velero ::: :::BlockQuote{indent="1"} $ kubectl set image deployment/velero velero=velero/velero\:v1.10.2 --namespace velero ::: :::Paragraph{indent="1"} **Note: **This update may take a minute in order to get the new pods rolled out. ::: 7. Confirm that both the client and server versions are on the same 1.10.2 release: :::BlockQuote{indent="1"} $ ./velero version ::: 8. When the upgrade is complete, login to the Turbine Installer dashboard (https\://\:8800). 9. Go to the Version History tab - you will see a version for 23.5.1 10. Click **Deploy** once the preflight checks have completed. 11. A new configuration is needed for the Elasticsearch persistent volume size and storageclass. Recommended sizes for small/medium/large environments are 8GB/16GB/32GB respectively. 12. Once the Application tab shows ‘Ready’ your upgrade is complete. ## Upgrade Turbine on Embedded Airgap Cluster Installations ### Prerequisites - Turbine version 23.2.x+If you are not on a version that is >= 11.0, contact your Swimlane support representative. - MongoDB 5.0.14 - Links to the Offline Installer Package and Offline Airgap Bundle If you do not have these linked, 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. ### Upgrade Instructions 1. Copy the latest offline installer package to each airgapped server.Untar the offline installer package on each server. :::BlockQuote{indent="1"} $ tar -xzvf turbine-23.3.2.tar.gz ::: 2. Scale down EKCO and kotsadm-rqlite. `kubectl scale deployment ekc-operator --replicas=0 -n kurl ` `kubectl scale statefulsets kotsadm-rqlite --replicas=0 -n default` 3. Run the Turbine Platform Installer update on any node in your deployment: :::BlockQuote{indent="1"} $ cat install.sh | sudo bash -s airgap ha ::: 4. 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: `cat ./tasks.sh | sudo bash -s load-images ` Have images been loaded on node swimlane-2? (Y/n) 5. Run :::BlockQuote{indent="1"} cat ./tasks.sh | sudo bash -s load-images ::: :::Paragraph{indent="1"} on nodes two (2) and node three (3) before proceeding to run the command on node one (1).This command can be run simultaneously on nodes 2 and 3. Once the load-images script completes on nodes 2 and 3, enter *Y* in the node 1 terminal session twice. ::: 6. When the upgrade script completes, press **Enter **on node 1 and then upload the airgap bundle to the SPI dashboard. 7. Log in to the Turbine Platform Installer dashboard (https\://\:8800). 8. Go to the Version History tab and click **Upload a new version**, then browse to the turbine-23.3.2.airgap file and click **Upload**. a. The sequence number “\_372” of the airgap file may be higher than shown if a new sequence has been published b. Once the upload of the airgap completes, refresh the page or switch tabs to see the status of the file extraction. 9. Go back to the Version History tab and Click on configure on 23.5.1\_372 10. Scroll down for **Swimlane Logging Level **change default warn to info and save the config 11. Go back to the Version History tab and click **Deploy** on the new 23.5.1 version at the top of the versions list. 12. Once the Application tab shows ‘Ready’ your upgrade is complete. Upgrade Turbine on Existing Airgap Cluster Installations Prerequisites ------------- - Turbine version 23.2.x+ If you are not on a version that is > 11.0, contact your Swimlane support representative. - MongoDB 5.0.14 - Kubernetes 1.22-1.27 - KOTS kubectl plugin 1.105.1 - Velero 1.10-.x **Important! **Swimlane recommends that you perform a MongoDB backup prior to starting this update. For more information, see Backup and Restore on an Existing Cluster with Snapshots. ### Upgrade Instructions 1. SSH into any node in your deployment. 1. Download the Swimlane Turbine Installer kubectl add-on for the OS version where you run kubectl commands from: Linux: https\://get.swimlane.io/turbine/existing-cluster/install/linux OSX: https\://get.swimlane.io/turbine/existing-cluster/install/osx 2. Download the latest SPI offline package: https\://get.swimlane.io/existing-cluster/install/offline-package 2. Copy the latest SPI Kubectl Add-on and SPI offline packages to your jumpbox: :::BlockQuote{indent="1"} $ scp kotsadm.tar.gz user@\:/tmp/kotsadm.tar.gz ::: :::BlockQuote{indent="1"} $ scp kots\_\.tar.gz user@\:/tmp/kots\_\.tar.gz ::: 3. Untar the SPI Kubectl Add-on: :::BlockQuote{indent="1"} $ tar -zxvf kots\_\.tar.gz ::: 4. Rename or remove the *original* kubectl-kots file: :::BlockQuote{indent="1"} $ rm /usr/local/bin/kubectl-kots ::: 5. Rename and move the *latest*SPI Kubectl Add-on file to /usr/local/bin/kubectl-kots. :::BlockQuote{indent="1"} $ mv kots kubectl-kots ::: :::BlockQuote{indent="1"} $ mv kubectl-kots /usr/local/bin/ ::: 6. Download Velero 1.10.2 to the jumpbox for the jumpbox's OS version: https\://github.com/vmware-tanzu/velero/releases/tag/v1.10.2 7. Untar the file and then change directory into the uncompressed directory: :::BlockQuote{indent="1"} $ tar -zxf \.tar.gz ::: :::BlockQuote{indent="1"} $ cd \ ::: 8. Update Velero custom resource definitions: :::BlockQuote{indent="1"} $ ./velero install --crds-only --dry-run -o yaml | kubectl apply -f - ::: 9. Download the new Velero images and push them to your private registry from your jumpbox. For specific steps on how to download and push new Velero images, see Download and Push New Velero Images. 10. Update the images Velero and Restic are using to 1.10.2 (this update will take a minute to get new pods rolled out): :::BlockQuote{indent="1"} $ kubectl set image daemonset/restic restic=\/\velero/velero\:v1.10.2 --namespace velero ::: :::Paragraph{indent="1"} Confirm both client and server version are on the same 1.10.2 release: ::: :::BlockQuote{indent="1"} $ kubectl set image deployment/velero velero=\/\velero/velero\:v1.10.2 --namespace velero ::: :::Paragraph{indent="1"} **Note: **This update may take a minute in order to get the new pods rolled out. ::: 11. Confirm both client and server version are on the same 1.10.2 release: :::BlockQuote{indent="1"} $ ./velero version ::: 12. Push the SPI (kotsadm) images to your registry: :::BlockQuote{indent="1"} $ kubectl kots admin-console push-images kotsadm.tar.gz \/\ --registry-username \ --registry-password \ ::: 13. Next, upgrade the Swimlane Platform Installer (SPI): :::BlockQuote{indent="1"} $ kubectl kots admin-console upgrade --kotsadm-registry \/\ --registry-username \ --registry-password \ -n \ ::: :::Paragraph{indent="1"} When the SPI upgrade is complete, upload the Turbine airgap bundle to the SPI dashboard. ::: 14. Log in to the Swimlane Platform Installer dashboard (https\://\:8800). 15. Go to the Version History tab and click **Upload a new version**, then browse to the turbine-23.5.1.airgap file and click **Upload**. a. The sequence number “\_372” of the airgap file may be higher than shown if a new sequence has been published. b. Once the upload of the airgap completes, refresh the page or switch tabs to see the status of the file extraction. 16. Go to the Version History tab - you will see a version for 23.5.1 and Click on configure 17. Scroll down for **Swimlane Logging Level **change default warn to info and save the config 18. Click Deploy on the new 23.5.1 version with the highest sequence number at the top of the versions list. 19. Once the Application tab shows ‘Ready’ your upgrade is complete.