sudo
access on all nodes and a non-zero UID:
cd
into the directory that it creates.
ae5_conda
environment by running the following commands:
HOSTNAME
environment variable to populate the k3s_values.yaml
file. To use a different hostname, edit that file or include the --hostname <HOSTNAME>
argument in your pre-install script command.--single-node
argument in the pre-install script command to skip instructions for adding nodes and use the anaconda-storage
volume for managed persistence.k3s_preinstall.sh
script produces two files: k3s_values.yaml
and NEXT_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, the k3s_preinstall.sh
script 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 the NEXT_STEPS.txt
file.
./k3s_preinstall.sh
command as many times as is necessary. No destructive actions are performed on your cluster by running the pre-install script.
k3s_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.
anaconda-enterprise-k3s-*
directory and install K3s by running the following command:
anaconda-enterprise-k3s-*
directory, or you can wait until the images are fully uploaded to continue.
k3s_values.yaml
contains the expected Workbench configuration values.
Ready
and Running
states.