Turbine 24.3.4 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.4 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-4 | 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.4 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.4.

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.4.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)

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.

Go to the Version History tab and click Upload a new version, then browse to the turbine-24.3.4.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.4 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.4 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

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.

Go to the Version History tab, click Upload a new version, then browse the turbine-24.3.4.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.4 and Click on configure.

Click Deploy on the new 24.3.4 version at the top of the versions list.

Once the Application tab shows ‘Ready’ your upgrade is complete.