Bring Your Own Kubernetes (BYOK8s) Upgrade¶
Contact the Anaconda implementation team before you begin for assistance upgrading your version of Anaconda Enterprise 5. It is intended for you to follow along with these instructions as an Anaconda Implementation team member guides you through the upgrade process. They will provide you with a Helm Chart archive that contains all the necessary components needed for upgrading.
Caution
Project sessions are terminated during the upgrade process! Because of this, it is important to stop all sessions prior to upgrading. If you do not, sessions that are terminated as part of the upgrade process must be restarted manually post upgrade.
Sessions can be stopped programmatically using
ae5-tools
by running the following command in a terminal that has access your Anaconda Enterprise cluster over the network:
Prerequisites¶
You must have access to the Administrative Server.
You must verify the Service Account used for the upgrade has the correct permissions.
Air-gapped servers must have the Docker images added to their Docker image repository.
Upgrade process¶
Upgrade your BYOK8s cluster by performing the following steps:
Log in to the service account on the Administrative Server running your Anaconda Enterprise software.
Unpack the Helm Charts provided by Anaconda onto the Administrative Server:
Save your current configurations with the
extract_config.sh
script delivered with your Helm Chart by running the following command:The
extract_config.sh
script creates a file calledhelm_values.yaml
and saves it in the directory where the script was run.Verify the information captured in
helm_values.yaml
file is correct and contains all of your current cluster configuration settings.Begin the upgrade by running the following command:
If the upgrade is successful, your output will look like this:
The duration of the upgrade depends on both the cluster node count and the speed of the new docker images loading into each node. You can view the status of the upgrade process by running the following command:
Once all pods display a Running status and each pod is running all their containers, you may return to using the cluster as normal.