Turbine 26.2.3 Upgrade Instructions

use these instructions to upgrade your instance to turbine 26 2 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 red hat 8 is no longer supported beginning with turbine 26 2 3 as part of the turbine 26 2 3 embedded cluster upgrades, kubernetes is updated to version 1 34 4 which does not support red hat 8 (specifically, linux kernel versions 4 18 and earlier) customers with embedded clusters running red hat 8 must upgrade to red hat 9 before upgrading to turbine 26 2 3 mandatory prerequisites to upgrade mongodb to version 8 0 before upgrading mongodb to version 8 0, perform the following steps to check the current configuration and update it if needed 1\ verify mongodb compatibility 1 1 connect to mongodb as an admin (replace \<namespace> with your actual namespace) kubectl exec it n \<namespace> mongo 0 mongosh u admin p authenticationdatabase admin tls tlsallowinvalidcertificates admin note you will be prompted to enter your mongodb admin password 1 2 check the current mongodb version (it should display 8 0 x) use admin db version() db system version find() 1 3 verify the feature compatibility version db admincommand({ getparameter 1, featurecompatibilityversion 1 }) 1 4 update the feature compatibility version (if required) if the version does not include 8 0, update it db admincommand({ setfeaturecompatibilityversion '8 0' }) upgrade turbine on embedded cluster installations use the following instructions to upgrade turbine on an embedded cluster installation prerequisites turbine version 25 5 1 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 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 curl ssl https //kurl sh/turbine turbine 26 2 3 | sudo bash s ha note if selinux, a firewall, or a proxy is configured, append the following to the command 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 log in to the turbine platform installer dashboard https //\<swimlanedns> 8800 go to the version history tab and click check for updates in the pop up window, click go to the updated version , then click configure click deploy on version 26 2 3 with the highest sequence number once the application tab shows ‘ready’ , your upgrade is complete upgrade turbine on existing cluster installations prerequisites turbine version 25 5 1 mongodb 8 0 24 kubernetes 1 34 4 kots kubectl plugin 1 130 7 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) curl lo https //github com/replicatedhq/kots/releases/download/v1 130 7/kots linux amd64 tar gz macos (apple silicon / arm64) curl lo https //github com/replicatedhq/kots/releases/download/v1 130 7/kots darwin arm64 tar gz 1 2 untar the downloaded file tar zxf \<file name> tar gz 1 3 rename the kots binary to kubectl kots mv kots kubectl kots 1 4 move the kubectl kots binary into your path (e g /usr/local/bin/) sudo mv kubectl kots /usr/local/bin/ 1 5 run the upgrade command kubectl kots admin console upgrade n \<namespace> 2\ complete the upgrade from the ui log in to the turbine platform installer dashboard https //\<swimlanedns> 8800 go to the version history tab — you will see version 26 2 3 click deploy once the preflight checks have completed update the elasticsearch configuration configure the persistent volume size and storage class recommended sizes 8gb / 16gb / 32gb for small/medium/large environments once the application tab shows ‘ready’ , your upgrade is complete 💡 note replace \<file name> with kots linux amd64 kots darwin arm64 upgrade turbine on embedded airgap cluster installations prerequisites turbine version 25 5 1 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 tar xzvf turbine 26 2 3 tar gz 1 3 run the turbine platform installer update on any node in your deployment cat install sh | sudo bash s airgap ha provide the absolute path for kubernetes 1 34 4 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 cat /tasks sh | sudo bash s load images you will be prompted 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) 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 //\<swimlanedns> 8800 go to the version history tab and click upload a new version , then browse to the turbine 26 2 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 2 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 25 5 1 mongodb 8 0 24 kubernetes 1 34 4 kots kubectl plugin 1 130 7 velero 1 18 2 turbine 26 2 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) curl lo https //github com/replicatedhq/kots/releases/download/v1 130 7/kots linux amd64 tar gz 1 2 download the latest spi offline package 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 scp kots \<os version> tar gz user@\<swimlanedns> /tmp/kots \<os version> tar gz scp kotsadm tar gz user@\<swimlanedns> /tmp/kotsadm tar gz 1 4 untar the spi kubectl add on tar zxvf kots \<os version> tar gz 1 5 rename or remove the original kubectl kots file rm /usr/local/bin/kubectl kots 1 6 rename and move the latest spi kubectl add on file to /usr/local/bin/ mv kots kubectl kots sudo mv kubectl kots /usr/local/bin/ 1 7 push the spi (kotsadm) images to your registry kubectl kots admin console push images kotsadm tar gz \<your registry endpoint>/\<your registry name> \ registry username \<username> registry password \<password> 1 8 upgrade the swimlane platform installer (spi) kubectl kots admin console upgrade \ kotsadm registry \<your registry endpoint>/\<your registry name> \ registry username \<username> \ registry password \<password> \ n \<namespace> when the spi upgrade is complete, upload the turbine airgap bundle to the spi dashboard 2\ complete the upgrade from the ui log in to the swimlane platform installer dashboard https //\<swimlanedns> 8800 go to the version history tab and click upload a new version , then browse to the turbine 26 2 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 completes, refresh the page or switch tabs to see the status of the file extraction go to the version history tab — you will see version 26 2 3 , then click configure click deploy on the new 26 2 3 version at the top of the versions list once the application tab shows ‘ready’ , your upgrade is complete general note if you face any issues downloading kubernetes download and copy kubernetes 1 34 4 tar gz on each server the file can be downloaded on the jump server using curl lo https //kurl sh/bundle/version/v2026 07 08 0/turbine stable multitenant/packages/kubernetes 1 34 4 tar gz known issue 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