Upgrade a Cluster - Kubernetes Classic
This page walks you through upgrading a TigerGraph cluster in Kubernetes. Upgrading a cluster requires several minutes of downtime.
Kubernetes Classic is Deprecated
This feature is part of our Kubernetes Classic support, which is now deprecated. New designs should not use this feature. Future Kubernetes support will use Kubernetes Operators.
|Not every version can be upgraded directly to any other version. Depending on the version you are upgrading from, you may need to upgrade to another version first before upgrading to the target version. See Upgrading an Existing Installation for restrictions for details on upgrade restrictions.|
A running TigerGraph Deployment in a Kubernetes cluster
You have configured
kubectlfor access to your running Kubernetes cluster
2.1. Download script
Clone the repository at https://github.com/tigergraph/ecosys.
Change into the
There is a script named
tg that you need to perform the actions described in this page.
2.2. Upgrade cluster
Run the following command to upgrade your cluster:
$ ./tg upgrade <cloud_provider> upgrade -v <target_version> -n <namespace> --prefix <prefix>
<cloud_platform>with the cloud platform where your Kubernetes cluster is provisioned. Possible values are:
<namespace>with the namespace where your resources reside. If not provided, the script uses the default namespace
<prefix>with the Pod name prefix you used when you created the cluster. If you didn’t specify a prefix when creating the cluster, do not specify one here.
For example, to upgrade a cluster in namespace
example to 3.7.0 from 3.6.1, which is an eligible version to upgrade from to 3.7, run the following command:
$ ./tg eks upgrade -v 3.7.0 -n example