Upgrading a Cluster

You can check whether there is a new latest version available for your Octelium Cluster as follows:

octops upgrade <DOMAIN> --check

You can upgrade a Cluster to the latest version as follows:

octops upgrade <DOMAIN>

note

If you installed the Cluster via the quick installation guide, then use the kubeconfig path /etc/rancher/k3s/k3s.yaml as shown in detail here.

By default, the command uses the kubeconfig located at $HOME/.kube/config or if explicitly set by the KUBECONFIG environment variable. You can also explicitly set the underlying Kubernetes cluster kubeconfig file path via the --kubeconfig flag as follows:

octops upgrade <DOMAIN> --kubeconfig </PATH/TO/CLUSTER/KUBECONFIG>

By default the command starts upgrading the Cluster to the latest version. You can set a specific version using the --version flag as follows:

octops upgrade <DOMAIN> --kubeconfig </PATH/TO/CLUSTER/KUBECONFIG> --version <VERSION>

Upgrading the Cluster is done from within the kubernetes cluster itself by starting Genesis as Kubernetes job to initiate the upgrade process. The whole operation should usually take a few minutes minutes depending on the performance and specs of the underlying kubernetes nodes. By default, the octops upgrade command immediately exits after starting the Genesis pod without waiting it to finish. You can, however, explicitly instruct the command to command until the Genesis job pod finishes the upgrade via the --wait flag as follows:

octops upgrade <DOMAIN> --wait