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 log in to the swimlane platform installer dashboard (https //\<swimlanedns> 8800) 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 log in to the swimlane platform installer dashboard (https //\<swimlanedns> 8800) 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 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 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 \<nam espace> when the spi upgrade is complete, upload the swimlane airgap bundle to the spi dashboard 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 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