Swimlane 10.13.2 Upgrade Instructions

Use these upgrade instructions to upgrade your instance of Swimlane 10.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 Swimlane on Embedded Cluster Installations

Use the following instructions to upgrade this version of Swimlane on an embedded cluster installation.

Prerequisites:

Swimlane version 10.12+ If you are not on a version that is >= 10.12, contact your Swimlane support representative. Upgrades from 10.13.0+ can skip to step 5.

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:

SSH into the any node in your deployment and execute the following command to begin the Swimlane Platform Installer component upgrade: $ curl -sSL https://kurl.sh/swimlane-platform-stable-10-13-2 | sudo bash -s ha NOTE: If you have configured SELinux, add this to the end of the command above: installer-spec-file=se.yaml

For a multi-node (HA) cluster, the script prompts you to drain node one (1) and apply the upgrade. Once the upgrade on node one (1) is complete, the process continues running. It then asks for confirmation to drain node two (2) as well as a command to run in that node.See this example:

✔ Kubernetes host packages installed node/ip-10-1-0-147.swimlane.io already uncordoned Drain node ip-10-1-0-186.swimlane.io to prepare for upgrade? (Y/n) y ... pod/swimlane-syslog-receiver-86f79c8fd6-2rvwt evicted pod/swimlane-tasks-5dfd4d5f94-tkrb2 evicted node/ip-10-1-0-186.swimlane.io evicted Run the upgrade script on remote node to proceed: ip-10-1-0-186.swimlane.io curl https://kurl.sh/swimlane-platform-stable-10-13-0/upgrade.sh | sudo bash -s kubernetes-version=1.24.4

Run the upgrade command on the node that was drained. Use kubectl get nodes -o wide to find the IP of the node that was drained. The primary script that ran in node 1 will detect that node 2 has been upgraded, and will now ask to drain and upgrade node three (3). Follow the same steps for node 2 to complete the kubernetes portion of the upgrade.

Once the additional nodes are complete, press Enter in the terminal window of the first node in which you ran the install command to complete the installation.

Go to the Version History tab and look for the new published version If this version doesn’t show up initially, click Check For Updates.

A pop-up window appears, click Go to updated version, select the and click on configure

scroll down for new configuration options under the Ingress Settings section to enable and optionally override HTTP CORS and CSP headers for Swimlane Web. If left to their default values, no CORS or CSP headers will be set for Swimlane Web.

Click Deploy on the new 10.13.2 version with the highest sequence number at the top of the versions list.

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

See Update the Swimlane Python Driver Python Package if you want to update the driver at this time.

Upgrade Swimlane on Existing Cluster Installations

Prerequisites:

Swimlane version 10.6 or greater If you are not on a version that is > 10.6, contact your Swimlane support representative.

MongoDB 5.0.14

Kubernetes 1.22-1.25

KOTS kubectl plugin 1.96.3

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:

Download the latest SPI kubectl add-on for the OS version where you run kubectl commands from: $ curl https://kots.io/install/v1.96.3 | bash $ kubectl kots version The KOTS kubectl plugin version should match what is listed in the prerequisites above.

Next, upgrade the Swimlane Platform Installer (SPI): $ kubectl kots admin-console upgrade -n <namespace>

Download Velero 1.10.2 for your OS version: https://github.com/vmware-tanzu/velero/releases/tag/v1.10.2 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 -

Velero 1.10 replaces the restic daemonset with node-agent. Upgrade the container images as instructed in Velero upgrade to 1.10 article.

Confirm that both the client and server versions are on the same 1.10.2 release: $ ./velero version

Go to the Version History tab and look for the new published version If this version doesn’t show up initially, click Check For Updates.

A pop-up window appears, click Go to updated version and select the 10.13.2 version with the highest suffix version at the top of the versions list.or visit the Version History tab and click Configure.

Scroll down to see new configuration options under the Ingress Settings section to enable and optionally override HTTP CORS and CSP headers for Swimlane Web. If left to their default values, no CORS or CSP headers will be set for Swimlane Web.

Click Deploy on the new 10.13.2 version with the highest sequence number at the top of the versions list.

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

See Update the Swimlane Python Driver Python Package if you want to update the driver at this time.

Upgrade Swimlane on Embedded Airgap Cluster Installations

Prerequisites

Swimlane version 10.12+If you are not on a version that is >= 10.12, 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:

Copy the latest offline installer package to each airgapped server.Untar the offline installer package on each server. $ tar -xzvf swimlane-platform-10.13.2_549.tar.gz

Run the Swimlane Platform Installer update on any node in your deployment: $ cat install.sh | sudo bash -s airgap ha

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 on nodes 2 and 3, enter Y in the node 1 terminal session twice.

The install script now runs on node 1 for a few minutes. Once it completes, follow the prompts to run the upgrade script on nodes 2 and 3, similar to this example (the IP address will depend on your deployment):

✔ Kubernetes host packages installed node/ip-10-1-0-147.swimlane.io already uncordoned Drain node ip-10-1-0-186.swimlane.io to prepare for upgrade? (Y/n) y ... pod/swimlane-syslog-receiver-86f79c8fd6-2rvwt evicted pod/swimlane-tasks-5dfd4d5f94-tkrb2 evicted node/ip-10-1-0-186.swimlane.io evicted Run the upgrade script on remote node to proceed: ip-10-1-0-186.swimlane.io cat upgrade.sh | sudo bash -s kubernetes-version=1.24.4 docker-registry-ip=10.96.3.115

When both upgrade scripts are complete, 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 swimlane-platform-10.13.2_549.airgap file and click Upload.

The sequence number 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 back to the Version History tab and Click on configure on the 10.13.2 release with the highest suffix number.

Scroll down to see new configuration options under the Ingress Settings section to enable and optionally override HTTP CORS and CSP headers for Swimlane Web. If left to their default values, no CORS or CSP headers will be set for Swimlane Web.

Click Deploy on the 10.13.2 version with the highest suffix number.

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

See Update the Swimlane Python Driver Python Package if you want to update the driver at this time.

Upgrade Swimlane on Existing Airgap Cluster Installations Prerequisites

Swimlane version 10.6+ If you are not on a version that is > 10.6, contact your Swimlane support representative.

MongoDB 5.0.14

Kubernetes 1.22-1.25

KOTS kubectl plugin 1.96.3

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:

Download the latest SPI Kubectl Add-on Linux: https://get.swimlane.io/existing-cluster/install/linux OSX: https://get.swimlane.io/existing-cluster/install/osx

Download the latest SPI offline package: https://get.swimlane.io/existing-cluster/install/offline-package

Copy the latest SPI Kubectl Add-on and SPI offline packages 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

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/

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

Untar the file and then change directory into the uncompressed directory: $ tar -zxf <FILENAME>.tar.gzcd <DIRECTORY>

Update Velero custom resource definitions: $ ./velero install --crds-only --dry-run -o yaml | kubectl apply -f -

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.

Velero 1.10 replaces the restic daemonset with node-agent. Upgrade the container images as instructed in this Velero upgrade to 1.10 article.

Confirm both client and server version are on the same 1.10.2 release: $ ./velero version

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 Swimlane airgap bundle to the SPI dashboard.

Go to the Version History tab and click Upload a new version, then browse to the swimlane-platform-10.13.2_549.airgap file and click Upload.

The sequence number “_546” 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 - locate the version for 10.13.2 with the highest suffix number and click Configure.

Scroll down to see new configuration options under the Ingress Settings section to enable and optionally override HTTP CORS and CSP headers for Swimlane Web. If left to their default values, no CORS or CSP headers will be set for Swimlane Web.

Click Deploy on the new 10.13.2 version with the highest sequence number at the top of the versions list.

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

See Update the Swimlane Python Driver Python Package if you want to update the driver at this time.