Swimlane 10.11.3 Upgrade Instructions

use these instructions to upgrade your instance of swimlane 10 x upgrade swimlane 10 11 3 480 on embedded online cluster installations use the following instructions to upgrade this version of swimlane on an embedded cluster installation prerequisites swimlane version 10 6 or greater if you are not on a version that is > 10 6, contact your swimlane support representative mongodb 4 4 11 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 and execute the following commands to begin the swimlane platform installer component upgrade $ kubectl annotate crd prometheuses monitoring coreos com kubectl kubernetes io/last applied configuration $ curl ssl https //kurl sh/swimlane platform stable 10 11 3 | sudo bash s ha load balancer address=\<swimlanedns> 6443 note if you have configured selinux, append this to the command above installer spec file=se yaml0 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 testing scott qa spt 7770 1/upgrade sh | sudo bash s kubernetes version=1 21 14✔ 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 testing scott qa spt 7770 1/upgrade sh | sudo bash s kubernetes version=1 21 14 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 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 version 10 11 3 480if this version doesn’t show up initially, click check for updates a pop up window appears, click go to updated version click deploy on the new 10 11 3 480 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 10 11 3 480 on existing online 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 4 4 11 kubernetes 1 19 1 24 kots kubectl plugin 1 90 0 velero 1 9 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 spi kubectl add on version 1 90 0 $ curl https //kots io/install/1 90 0 | bash next, upgrade the swimlane platform installer (spi) $ kubectl kots admin console upgrade n \<namespace> download velero 1 9 2 for your os version https //github com/vmware tanzu/velero/releases/tag/v1 9 2 for example $ curl ssl https //github com/vmware tanzu/velero/releases/download/v1 9 2/velero v1 9 2 linux amd64 tar gz o velero v1 9 2 linux amd64 tar gz 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 $ kubectl set image daemonset/restic restic=velero/velero\ v1 9 2 namespace velero note this update may take a minute in order to get the new pods rolled out update the images velero and restic use to 1 9 2 $ kubectl set image deployment/velero velero=velero/velero\ v1 9 2 namespace velero confirm that both the client and server versions are on the same 1 9 2 release $ /velero version log in to the swimlane platform installer dashboard (https //\<swimlanedns> 8800) go to the version history tab and look for version 10 11 3 480 if this version doesn’t show up initially, click check for updates if you are asked to configure, scroll to postgresql on postrgresql settings, input values for the required fields and then click save config postgresql requires a persistent volume, so you must set a pvc storageclass the default size is 8 gb a pop up window appears, click go to updated version or visit the version history tab click deploy on the new 10 11 3 480 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 10 11 3 480 on embedded 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 4 4 11 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 11 3 471 tar gz run this command on any node in your deployment before the upgrade can start, it removes an annotation from a prometheus resource $ kubectl annotate crd prometheuses monitoring coreos com kubectl kubernetes io/last applied configuration run the swimlane platform installer update on any node in your deployment $ cat install sh | sudo bash s airgap ha once the install 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) installation complete ✔ run this script on all remote nodes to apply changes cat upgrade sh | sudo bash s airgap docker registry ip=10 96 3 115 press enter to proceed 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 look for version 10 11 3 480 if this version doesn’t show up initially, click check for updates browse to the swimlane platform 10 11 3 480 airgap file and click upload 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 deploy on the new 10 11 3 480 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 10 11 3 480 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 4 4 11 kubernetes 1 19 1 24 kots kubectl plugin 1 90 0 velero 1 9 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 spi kubectl add on version 1 90 0 $ curl ssl https //github com/replicatedhq/kots/releases/download/v1 90 0/kots linux amd64 tar gz o kots linux amd64 tar gz download the latest spi offline package https //get swimlane io/existing cluster/install/offline package copy the spi kubectl add on and spi offline packages to your jumpbox $ scp kots linux amd64 tar gz user@\<swimlanedns> /tmp/kots linux amd64 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 9 2 to the jumpbox for the jumpbox's os version https //github com/vmware tanzu/velero/releases/tag/v1 9 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 update the images velero and restic are using to 1 9 2 (this update will take a minute to get new pods rolled out) $ kubectl set image deployment/velero velero=\<my registry>/\<my namespace>velero/velero\ v1 9 2 namespace velero $ kubectl set image daemonset/restic restic=\<my registry>/\<my namespace>velero/velero\ v1 9 2 namespace velero note this update may take a minute in order to get the new pods rolled out confirm both client and server version are on the same 1 9 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 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 11 3 480 airgap file and click upload 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 10 11 3 480 if you are asked to configure, scroll to postgresql on postgresql settings, input the values for the required fields and then click save config postgresql requires a persistent volume, so you must set a pvc storageclass the default size is 8 gb a pop up window appears, click go to updated version or visit the version history tab click deploy on the new 10 11 3 480 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 update the swimlane python driver python package beginning with swimlane version 10 2 0, the python driver swimlane python package must be manually updated after an upgrade delete the old swimlane python package update the swimlane python package in the swimlane ui to version 10 9 1 if this is an embedded airgapped upgrade, please download the swimlane python wheel ( whl) package from here and update it in the swimlane ui restart the swimlane api and tasks pods with this command kubectl rollout restart deployments/swimlane api deployments/swimlane tasks download and push new velero images use these commands to download and push new velero images $ docker pull velero/velero\ v1 9 2 $ docker tag velero/velero\ v1 9 2 \<my registry>/\<my namespace>/velero/velero\ v1 9 2 $ docker push \<my registry>/\<my namespace>/velero/velero\ v1 9 2 $ docker pull velero/velero restic restore helper\ v1 9 2 $ docker tag velero/velero restic restore helper\ v1 9 2 \<my registry>/\<my namespace>/velero/velero restic restore helper\ v1 9 2 $ docker push \<my registry>/\<my namespace>/velero/velero restic restore helper\ v1 9 2 $ docker pull velero/velero plugin for aws\ v1 5 0 $ docker tag velero/velero plugin for aws\ v1 5 0 \<my registry>/\<my namespace>/velero/velero plugin for aws\ v1 5 0 $ docker push \<my registry>/\<my namespace>/velero/velero plugin for aws\ v1 5 0 $ docker pull velero/velero plugin for gcp\ v1 5 0 $ docker tag velero/velero plugin for gcp\ v1 5 0 \<my registry>/\<my namespace>/velero/velero plugin for gcp\ v1 5 0 $ docker push \<my registry>/\<my namespace>/velero/velero plugin for gcp\ v1 5 0 $ docker pull velero/velero plugin for microsoft azure\ v1 5 0 $ docker tag velero/velero plugin for microsoft azure\ v1 5 0 \<my registry>/\<my namespace>/velero/velero plugin for microsoft azure\ v1 5 0 $ docker push \<my registry>/\<my namespace>/velero/velero plugin for microsoft azure\ v1 5 0 troubleshooting on rare occasion, pgpool has been reported to be in an unhealthy state after an update to remediate, restart the pgpool deployment object kubectl rollout restart deployment postgresql pgpool namespace \<namespace>