Turbine 24.3.5 Upgrade Instructions

turbine upgrade instructions use these upgrade instructions to upgrade your instance of turbine 24 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 for version 24 3 5 of the turbine platform, if you encounter any issues with swimlane tenant pods related to the database during a new installation, redeploy the application no action is required if you are upgrading upgrade turbine on embedded cluster installations use the following instructions to upgrade this version of swimlane on an embedded cluster installation prerequisites turbine version 24 3 2 mongodb 6 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 ssh into any node in your deployment scale down ekco and kotsadm rqlite note ekco and kotsadm rqlite will automatically scale back up after the script in step 3 has completed kubectl n kurl scale deployment ekc operator replicas=0 kubectl n default scale statefulsets kotsadm rqlite replicas=0 execute the following command to begin the turbine platform installer component upgrade curl ssl https //kurl sh/turbine turbine 24 3 5 | sudo bash s ha note if you have configured selinux, add this to the end of the command above installer spec file=se yaml after the install script has completed, log in to the turbine platform installer dashboard (https //\<swimlanedns> 8800) go to the version history tab and click check for updates a pop up window appears, click go to the updated version and click configure click deploy on the new 24 3 5 version with the highest sequence number at the top of the versions list once the application tab shows ‘ready’ your upgrade is complete upgrade turbine on existing cluster installations prerequisites turbine version 24 3 2 mongodb 6 0 14 kubernetes 1 25 1 30 kots kubectl plugin 1 117 3 velero 1 14 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 velero to 1 14 x verify if velero needs to be updated $ /velero version velero 1 14 includes a change that replaces the restic daemonset with the node agent daemonset depending on what version you are upgrading from, there are different steps for patching the container images see the velero docs upgrading to velero 1 14 for details download velero 1 14 x for your os version https //github com/vmware tanzu/velero/releases/tag/v1 14 0 untar the file and then change directory (cd) into the uncompressed directory tar zxf \<filename> tar gz $ cd \<directory> update velero custom resource definitions $ /velero install crds only dry run o yaml | kubectl apply f upgrade container images as instructed in the velero upgrade to 1 13 article, upgrade to 1 14 confirm that both the client and server versions are on the same 1 12 0 release $ /velero version upgrade kots addon and kots app prepare the swimlane turbine installer kubectl add on prepare the swimlane turbine installer kubectl add on 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 untar the file tar zxf kots \<os version> tar gz rename the kots binary to kubectl kots mv kots kubectl kots move the kubectl kotsbinary into your path so that it can be recognized by kubectl (e g /usr/local/bin/) mv kubectl kots /usr/local/bin/ run the upgrade command kubectl kots admin console upgrade n \<namespace> when the upgrade is complete, login to the turbine installer dashboard (https //\<swimlanedns> 8800) go to the version history tab you will see a version for 24 3 5 click deploy once the preflight checks have completed 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 once the application tab shows ‘ready’ your upgrade is complete upgrade turbine on embedded airgap cluster installations prerequisites turbine version 24 3 2if you are not on a version that is >= 24 3 2, contact your swimlane support representative mongodb 6 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 note if you are using version 24 3 2, the third step applies if you are already on version 24 3 4, you can ignore this step copy the latest offline installer package to each airgapped server untar the offline installer package on each server $ tar xzvf turbine 24 3 5 tar gz copy kubernetes 1 29 8 tar gz on each server the file could be downloaded in the jump server using the following command curl lo https //kurl sh/bundle/version/v2024 09 06 0/turbine stable multitenant/packages/kubernetes 1 29 8 tar gz scale down ekco and kotsadm rqlite kubectl scale deployment ekc operator replicas=0 n kurlkubectl scale statefulsets kotsadm rqlite replicas=0 n default run the turbine platform installer update on any node in your deployment $ cat install sh | sudo bash s airgap ha provide the absolute of path for kubernetes 1 29 8 tar gz , downloaded as part of step 2, when prompted during installation 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) run cat /tasks sh | sudo bash s load images 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, press enter on node 1 and then upload the airgap bundle to the spi dashboard 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 24 3 5 airgap file and click upload the sequence number " xxx" of the airgap file my 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 24 3 5 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 24 3 2 mongodb 6 0 14 kubernetes 1 25 1 30 kots kubectl plugin 1 117 3 velero 1 14 x turbine 24 3 5 airgap bundle from swimlane contact your swimlane support representative if you do not have a download link for this 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 velero to 1 14 x verify if velero needs to be updated $ /velero version velero 1 14 includes a change that replaces the restic daemonset with the node agent daemonset depending on what version you are upgrading from, there are different steps for patching the container images see the velero docs upgrading to velero 1 14 for details if already on velero 1 10+ download velero 1 14 to the jumpbox for the jumpbox's os version $ /velero install crds only dry run o yaml | kubectl apply f untar the file and then change directory (cd) into the uncompressed directory $ tar zxf \<filename> tar gz $ cd \<directory> update velero custom resource definitions https //github com/vmware tanzu/velero/releases/tag/v1 14 3 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 upgrade container images as instructed in the velero article confirm that both the client and server versions are on the same 1 12 release $ /velero version upgrade kots plugin and kots app download the latest spi kubectl add on see kots documentation for how to do so a versioned link will look like this \# linux amd https //github com/replicatedhq/kots/releases/download/v1 117 3/kots linux amd64 tar gz download the latest spi offline package curl l https //get swimlane io/existing cluster/install/offline package o kotsadm tar gz copy the latest spi kubectl add on and spi offline packages to your jumpbox $ scp kotsadm tar gz user@\<swimlanedns> /tmp/kotsadm tar gz $ scp kots \<os version> tar gz user@\<swimlanedns> /tmp/kots \<os version> tar gz untar the spi kubectl add on $ tar zxvf kots \<os version> tar gz rename or remove the original kubectl kots file $ rm /usr/local/bin/kubectl kots rename and move the latest spi kubectl add on file to/usr/local/bin/kubectl kots $ mv kots kubectl kots $ mv kubectl kots /usr/local/bin/ 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> next, 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 log in to the swimlane platform installer dashboard (https //\<swimlanedns> 8800) go to the version history tab, click upload a new version, then browse the turbine 24 3 5 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 file extraction go to the version history tab you will see a version for 24 3 5 and click on configure click deploy on the new 24 3 5 version at the top of the versions list once the application tab shows ‘ready’ your upgrade is complete