Pre-installation
Perform all actions from an administrative account that hassudo access on all nodes and a non-zero UID:
- SSH onto the primary node.
- Deliver the latest Workbench image tarball and K3s bundle to the primary node.
-
Unpack the K3s bundle and
cdinto the directory that it creates. -
Remove old installations of conda by running the following command:
-
Install and activate the
ae5_condaenvironment by running the following commands: -
Stage the K3s assets by running the following command:
The
- By default, the pre-install script uses the hostname stored in the
HOSTNAMEenvironment variable to populate thek3s_values.yamlfile. To use a different hostname, edit that file or include the--hostname <HOSTNAME>argument in your pre-install script command. - If you are performing a single-node install, supply the
--single-nodeargument in the pre-install script command to skip instructions for adding nodes and use theanaconda-storagevolume for managed persistence.
k3s_preinstall.shscript produces two files:k3s_values.yamlandNEXT_STEPS.txt. The pre-installation script is designed to coach you on the necessary actions you need to take to install if your system is not ready. For example, if you do not have your instance backed up, thek3s_preinstall.shscript will inform you that the backups are missing and tell you to perform a backup before proceeding. Once the script has completed, it saves the output to theNEXT_STEPS.txtfile.- If you have made an error during the pre-installation process, perform the pre-installation cleanup commands. and start over.
-
It is safe to run the
./k3s_preinstall.shcommand as many times as is necessary. No destructive actions are performed on your cluster by running the pre-install script.
- By default, the pre-install script uses the hostname stored in the
- Verify that both of the files produced by running the pre-installation script were successfully generated. If you cannot find the files, stop here and consult your Workbench support team to diagnose the failures and complete pre-installation successfully.
Installation
The following steps detail the conventional output of what thek3s_preinstall.sh script instructs you to do. However, the script makes adjustments to these steps based on your local environment and outputs them to the NEXT_STEPS.txt file. Review the file and, if the output diverges from these instructions, follow the instructions in the file instead.
- Log out of the server node, then log back in to pick up the environment changes that were made during the pre-installation process.
-
Navigate to the
anaconda-enterprise-k3s-*directory and install K3s by running the following command:This script installs and starts K3s, then uploads the Workbench images. The image upload process can take up to 30 minutes to complete, depending on your setup. -
Once the image uploads begin, you can continue with installation by opening a second terminal and navigating back to the
anaconda-enterprise-k3s-*directory, or you can wait until the images are fully uploaded to continue. -
If your cluster has multiple nodes, add them now by running the following command for each node:
-
Verify that the
k3s_values.yamlcontains the expected Workbench configuration values.Take your time and verify everything is correct! -
Once the Workbench images are fully loaded, install the Workbench application by running the following command:
-
Monitor your cluster’s resources while they stabilize to ensure there are no unexpected issues by running the following command:
Allow time for the pods to appear and move to the
ReadyandRunningstates. - Open a browser and navigate to your instance of Workbench.
- Log in to Workbench and explore the platform!

