--- title: Swimlane 10.19.1 Upgrade Instructions slug: 10x-upgrade-guides/swimlane-10191-upgrade-instructions docTags: createdAt: 2025-11-27T16:10:50.059Z --- Use these upgrade instructions to upgrade your instance of Swimlane 10.x. The instructions are divided into subsections within this document, guiding you through the upgrade process based on your specific installation type, whether it is an embedded installation or an existing cluster. **Note: If you previously upgraded to version 10.19.0, you must also perform the component upgrade as part of the 10.19.1 upgrade process, due to changes made to the components. ** ## Prerequisites: The prerequisites listed below are mandatory and must not be overlooked: - If you are already on **version 10.19.0**, no action is required. - If you are using version **10.18.x**, follow these steps to review and update your current configuration as needed before upgrading **MongoDB **to** version 7.0**. ### Verify MongoDB Compatibility 1. **Connect to MongoDB as Admin **(replace \ with your actual namespace): `kubectl exec -it -n swimlane-sw-mongo-0 -- mongosh -u Admin -p --authenticationDatabase admin --tls --tlsAllowInvalidCertificates admin` :::Paragraph{indent="1"} NOTE: You'll be prompted to enter your mongo Admin password. ::: 1. **Check the Current MongoDB Version** (should display 6.0x): `db.version()` 2. Verify the Feature Compatibility Version: :::Paragraph{indent="1"} `use admin` `db.system.version.find()` ::: 4. Update the Feature Compatibility Version (if required): If the version does not include 6.0, update it: :::Paragraph{indent="1"} `db.adminCommand({ setFeatureCompatibilityVersion: '6.0' })` ::: ## *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.18 or later If you are not on a version that is >= 10.18, contact your Swimlane support representative. - MongoDB 6.0.14 or later **Important! **Swimlane recommends that you perform a MongoDB backup before starting this update. For more information, see Backup and Restore on an Embedded Cluster with Snapshots. **If Swimlane uses an external MongoDB, scale down the cluster by setting the replicas for deployments and stateful sets (STS) to 0.** **Then upgrade your external MongoDB servers to version 6.0.14 and then follow the upgrade instructions.** During the startup of the external MongoDB process, use the following commands: :::BlockQuote \--tlsAllowConnectionsWithoutCertificates --tlsAllowInvalidCertificates ::: :::BlockQuote kubectl scale deploy \ -n \ --replicas=0kubectl scale sts \ -n \ --replicas=0 ::: ### Upgrade Instructions: 1. SSH into 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-19-1 | sudo bash -s ha` **NOTE**: If you have configured SELinux, add this to the end of the command above\:installer-spec-file=se.yaml 2. A Kubernetes upgrade may be required depending on the current version in your environment. 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. For 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-19-1/upgrade.sh | sudo bash -s kubernetes-version=1.28.7` 3. 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, and will now ask to drain and upgrade node 3. Follow the same steps for node 2 to complete the kubernetes portion of the upgrade. 4. 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. 5. Log in to the Swimlane Platform Installer dashboard (https\://\:8800). 6. Go to the Version History tab and locate the newly published version.If this version doesn’t appear initially, click **Check for Updates**. 7. A pop-up window appears, click **Go to updated version**. 8. Click **Deploy** on the new 10.19.1 version with the highest sequence number at the top of the versions list (currently 10.19.1\_XXX). 9. 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.18 or later If you are not on a version that is >= 10.18, contact your Swimlane support representative. - MongoDB 6.0.14 or later - Kubernetes 1.27 to 1.30 - KOTS kubectl plugin 1.121.0 - 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. ### Upgrading to Kotsadm v1.121.0: 1. Download the latest SPI kubectl add-on for the OS version where you run kubectl commands from: `$ curl https://kots.io/install/v1.121.0 | bash` `$ kubectl kots version` The KOTS kubectl plugin version should match what is listed in the prerequisites above. ### Upgrading to Velero 1.14: See the Velero documentation for details: Velero Docs - Upgrading to Velero 1.14 ### Upgrade the Swimlane KOTS application: 1. Next, upgrade the Swimlane Platform Installer (SPI): :::BlockQuote{indent="1"} $ kubectl kots admin-console upgrade -n \ ::: 2. Log in to the Swimlane Platform Installer dashboard (https\://\:8800). 3. Go to the Version History tab and locate the newly published version.If this version doesn’t show up initially, click **Check For Updates**. 4. A pop-up window appears, click **Go to updated version** or visit the **Version History** tab. 5. Click **Deploy** on the new 10.19.1 version with the highest sequence number at the top of the versions list. 6. 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.18 or laterIf you are not on a version that is >= 10.18, contact your Swimlane support representative. - MongoDB 6.0.14 or later - 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 air gapped server. Untar the offline installer package on each server. :::BlockQuote{indent="1"} $ tar -xzvf swimlane-platform-10.19.1\_XXX.tar.gz ::: 2. Downloand the Kubernetes-1.29.10 on each server. The file could be downloaded in the jump server using the following command. :::BlockQuote{indent="1"} curl -LO https\://kurl.sh/bundle/version/v2024.11.08-0/swimlane-platform/packages/kubernetes-1.29.10.tar.gz ::: 3. Run the Swimlane 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 the Swimlane Platform Installer update on any node in your deployment: 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: :::BlockQuote{indent="1"} Run this script on node swimlane-2 to load required images before proceeding: cat ./tasks.sh | sudo bash -s load-imagesHave images been loaded on node swimlane-2? (Y/n) ::: 5. 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. 6. 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): :::BlockQuote{indent="1"} ✔ Kubernetes host packages installednode/ip-10-1-0-147.swimlane.io already uncordonedDrain node ip-10-1-0-186.swimlane.io to prepare for upgrade? (Y/n) y...pod/swimlane-syslog-receiver-86f79c8fd6-2rvwt evictedpod/swimlane-tasks-5dfd4d5f94-tkrb2 evictednode/ip-10-1-0-186.swimlane.io evictedRun the upgrade script on remote node to proceed: ip-10-1-0-186.swimlane.iocat upgrade.sh | sudo bash -s kubernetes-version=1.28.7 docker-registry-ip=10.96.3.115 ::: 8. When both upgrade scripts are complete, press **Enter **on node 1 and then upload the airgap bundle to the SPI dashboard. 9. Log in to the Swimlane Platform Installer dashboard (https\://\:8800). 10. Go to the Version History tab and click **Upload a new version**, then browse to the swimlane-platform-10.19.1\_XXX.airgap file and click **Upload**. 1. The sequence number “\_XXX” of the airgap file may be higher than shown if a new sequence has been published. 2. Once the upload of the airgap completes, refresh the page or switch tabs to see the status of the file extraction. 11. Go back to the Version History tab and click **Deploy** on the new 10.19.1 version at the top of the versions list. 12. 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.18 or later If you are not on a version that is >= 10.18, contact your Swimlane support representative. - MongoDB 6.0.14 or later - Kubernetes 1.27-1.30 - KOTS kubectl plugin 1.121.0 - 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. ### Upgrading to Kotsadm v1.121.0: 1. Download the **KOTS** Kubectl Add-on\:Linux: `https://github.com/replicatedhq/kots/releases/download/v1.121.0/kots_linux_amd64.tar.gz` OSX: `https://github.com/replicatedhq/kots/releases/download/v1.121.0/kots_darwin_all.tar.gz` 2. Download the latest SPI offline package: :::BlockQuote{indent="1"} https\://github.com/replicatedhq/kots/releases/download/v1.121.0/kotsadm.tar.gz ::: 3. Copy the KOTS Kubectl Add-on and SPI offline packages from your jumpbox to each node: :::BlockQuote{indent="1"} $ scp kots\_\.tar.gz user@\:/tmp/kots\_\.tar.gz$ scp kotsadm.tar.gz user@\:/tmp/kotsadm.tar.gz ::: 4. Untar the SPI Kubectl Add-on: :::BlockQuote{indent="1"} $ tar -zxvf kots\_\.tar.gz ::: 5. Rename or remove the *original* kubectl-kots file: :::BlockQuote{indent="1"} $ rm /usr/local/bin/kubectl-kots ::: 6. Rename and move the *latest* SPI Kubectl Add-on file to /usr/local/bin/kubectl-kots: :::BlockQuote{indent="1"} $ mv kots kubectl-kots $ mv kubectl-kots /usr/local/bin/ ::: 7. Verify version: :::BlockQuote{indent="1"} $ kubectl kots version ::: ### Upgrading to Velero 1.14.x: - See the Velero documention for details. You’ll have to use a jumpbox to download the new images and move them over. Velero Docs - Upgrading to Velero 1.14 - Confirm both client and server version are on the same 1.14.0 release: :::BlockQuote{indent="1"} $ ./velero version ::: ### Upgrade the Swimlane KOTS application: 1. Push the SPI (kotsadm) images to your registry: :::BlockQuote{indent="1"} $ kubectl kots admin-console push-images kotsadm.tar.gz \/\ --registry-username \ --registry-password \ ::: 2. 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 Swimlane airgap bundle to the SPI dashboard. ::: 3. Log in to the Swimlane Platform Installer dashboard (https\://\:8800). 4. Go to the Version History tab and click **Upload a new version**, then browse to the swimlane-platform-10.19.1\_XXX.airgap file and click **Upload**. 1. The sequence number “\_XXX” of the airgap file may be higher than shown if a new sequence has been published 2. Once the upload of the airgap completes, refresh the page or switch tabs to see the status of the file extraction. 5. Go to the Version History tab - you will see a version for 10.19.1\_XXX. 6. Click Deploy on the new 10.19.1\_XXX version with the highest sequence number at the top of the versions list. 7. 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. ## Update the Swimlane Python Driver Python Package **To update the Swimlane Python Driver package, see https\://support.swimlane.com/support/solutions/articles/8000109457-update-the-swimlane-python-driver-python-package.** ## Download and Push New Velero Images Use these commands to download and push new Velero images. :::BlockQuote $ docker pull velero/velero\:v1.14.0 $ docker tag velero/velero\:v1.14.0 \/\/velero/velero\:v1.14.0 $ docker push \/\/velero/velero\:v1.14.0 $ docker pull velero/velero-restic-restore-helper\:v1.14.0 $ docker tag velero/velero-restic-restore-helper\:v1.14.0 \/\/velero/velero-restic-restore-helper\:v1.14.0 $ docker push \/\/velero/velero-restic-restore-helper\:v1.14.0 $ docker pull velero/velero-plugin-for-aws\:v1.10.1 $ docker tag velero/velero-plugin-for-aws\:v1.10.1 \/\/velero/velero-plugin-for-aws\:v1.10.1 $ docker push \/\/velero/velero-plugin-for-aws\:v1.10.1 $ docker pull velero/velero-plugin-for-gcp\:v1.10.1 $ docker tag velero/velero-plugin-for-gcp\:v1.10.1 \/\/velero/velero-plugin-for-gcp\:v1.10.1 $ docker push \/\/velero/velero-plugin-for-gcp\:v1.10.1 $ docker pull velero/velero-plugin-for-microsoft-azure\:v1.10.1 $ docker tag velero/velero-plugin-for-microsoft-azure\:v1.10.1 \/\/velero/velero-plugin-for-microsoft-azure\:v1.10.1 $ docker push \/\/velero/velero-plugin-for-microsoft-azure\:v1.10.1 ::: ## Troubleshooting 1. Upgrading may occasionally leave the Hangfire notifications in a corrupted state, causing the swimlane-api and swimlane-tasks pods to crash loop with logs like the following: :::BlockQuote{indent="1"} swimlane-api\:Hangfire.Mongo.Migration.MongoMigrationException: Migration failed in Hangfire.Mongo.Migration.Steps.Version17.AddNotificationsCollectionswimlane-tasks\:Core.ErrorHandling.ContractRequiresException: RabbitMQConnectionString is not defined in Orchestration configuration. ::: :::Paragraph{indent="1"} Deleting the Hangfire notifications collection in MongoDB resolves this issue. ::: :::BlockQuote{indent="1"} kubectl exec swimlane-tools-0 -- /bin/bash -c 'mongo $SWIMLANE\_Data\_\_Mongo\_\_SwimlaneConnectionString --quiet --tls --tlsAllowInvalidCertificates --eval \\'db\["hangfire.notifications"].drop()\\'' :::