← back to ultihash.io

Update your cluster

How to apply update your UltiHash cluster's software and license

Updating your UltiHash cluster ensures that you are running the latest version of the software and that any license changes are properly applied. Updates are performed using Helm, which allows you to replace pods gradually (rolling updates) or force an update when required.

Rolling updates

Rolling updates allow you to safely apply updates to UltiHash components without causing downtime. This process replaces pods incrementally so that workloads continue to run while updated pods come online. Use rolling updates whenever you upgrade to a new version or make configuration changes.

How to perform a rolling update

  1. Confirm that the desired UltiHash version is available in the registry and ensure you have a backup of your configuration and data.

  2. Run the following Helm command:

helm upgrade <release_name> oci://registry.ultihash.io/stable/ultihash-cluster \
  -n <namespace> \
  --version 1.3.0 \
  --values values.yaml

  • Replace <release_name> with your Helm release name.

  • Replace <namespace> with the Kubernetes namespace where UltiHash is deployed.

  • Update 1.3.0 to the version you want to deploy.

  • If using a custom configuration, adjust values.yaml accordingly.

You can track the progress with:

kubectl get pods -n <namespace>

This will display pods terminating and new pods starting as the update rolls out.

License updates

When you update your UltiHash license through the user dashboard, the new license is automatically propagated to your cluster within one hour.

Apply a license update immediately

If you need the license change to take effect right away, you can force an update with Helm:

helm upgrade <release_name> oci://registry.ultihash.io/stable/ultihash-cluster \
  -n <namespace> \
  --version 1.3.0 \
  --values values.yaml \
  --force

  • Replace <release_name> with your Helm release name.

  • Replace <namespace> with the Kubernetes namespace where UltiHash is deployed.

  • Update 1.3.0 to match the version currently running.

The --force flag re-deploys all resources and applies the updated license immediately.

Last updated

Was this helpful?