Transition to SciSure Platform

This article describes connecting the admin console to the new SciSure delivery channel. Once the new connection is made, the new Labfolder releases will be available as usual.

The process includes the Kubernetes cluster update to ensure compatibility with the current Labfolder version. Depending on your current Kubernetes version, this update might not be necessary. However, it is highly recommended.

The Kubernetes update will cause a few minutes of downtime. All other steps in this tutorial do not have any downtime. Passwords, URLs, and data will remain the same.

Transition Steps

1. Download the current admin console configurations:

   kubectl kots get config -n default > config.yaml

2. Add the new license to the same directory you are executing this process. Please contact the Customer Success team at support@labfolder.com to request a license. Make sure the license file is named license.yaml:

   cat license.yaml

3. Verify the config.yaml file downloaded in the previous step is not empty. If it is empty, the process must stop because it will be difficult to recover the previous passwords:

   cat config.yaml

4. Remove the current admin console connection:

   kubectl kots remove labforward --force --namespace default

5. Connect with the SciSure release channel:

   kubectl kots install "labfolder-vulture/customers" --license-file license.yaml --config-values config.yaml --wait-duration "10m" --no-port-forward --namespace default

   1. If the preflight checks fail, access the admin console in the UI and fix possible issues. If you are familiar with this specific failure, ignore it. Then, click on "Deploy”.

6. Upgrade Kubernetes to version 1.33.5:

    curl -sSL https://kurl.sh/labfolder-vulture-customers | sudo bash

   1. You will be prompted to install the next Kubernetes version. For more details about the Kubernetes update, see Kubernetes Upgrade. This process can take between 10 minutes and 1 hour, depending on your current Kubernetes version.