> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Product and cluster upgrades

> Step-by-step upgrades for each surface - a cluster's version, a product version, and a platform components release.

Each part of the platform is upgraded in a different place. This page walks through all three surfaces. For who is allowed to perform each action, see [Version selection and admin guide](/platform/upgrades/version-selection#permissions).

## Upgrading a cluster

Each cluster runs a specific release version, chosen on the cluster itself - not in a central settings page.

### Choose a version when creating a cluster

1. Start creating a cluster (**Compute → Clusters → Create**).
2. In **Basic Information**, open the **Version** field (labelled *Cluster version to deploy*).
3. Pick a version. The newest version is selected for you by default.
4. Complete the rest of the form and select **Create Cluster**.

### Change the version of an existing cluster

1. Open the cluster and select **Edit**.
2. Change the **Version** field to the version you want.
3. Select **Update Cluster**.

Changing the version triggers a rollout. Clusters upgrade with a zero-downtime, automatically-recovering process - see [Rollbacks, failure modes, and recovery](/platform/upgrades/rollbacks-and-recovery#cluster-rollouts) and [Zero-downtime upgrades](/query/clusters/zero-downtime-upgrades).

<Warning>
  You cannot change the version while a cluster is mid-deployment or in a failed state. Wait for the cluster to return to a steady state, then edit it.
</Warning>

## Upgrading a product

Products are upgraded from one place: **Settings → Version Upgrades**. Each product appears as a row showing its current version and status. Only enabled products are listed - the optional products (Copilot, Laminar, Metriq) appear only when their feature is turned on; the Metadata Service is always available. See [Feature enablement and visibility](/platform/upgrades/version-selection#feature-enablement-and-visibility).

To upgrade a product:

1. Go to **Settings → Version Upgrades**.
2. On the product's row, open the version dropdown and select the target version.
3. Select **Upgrade**.

The **Upgrade** button stays disabled until you pick a version that differs from the current one, and while an upgrade is already in progress. While upgrading, the row shows **Upgrading…** and the status updates automatically; you'll get a confirmation when it finishes, or a failure notice if it doesn't.

<Info>
  Clusters are not in this list - they're versioned individually on each cluster. The **Version Upgrades** tab covers the products and the **Platform Components** section below.
</Info>

## Upgrading platform components

Platform components are upgraded together as a single **platform release**, from the **Platform Components** section at the top of **Settings → Version Upgrades**. The section shows the current platform version and its deployment status (Not deployed, Deploying, Deployed, Failed, Rolled Back, and so on).

<Info>
  A new workspace shows **Not deployed** here, and that's expected. Your platform components are set up and running from the moment the workspace is created - **Not deployed** simply means you haven't deployed a platform *release* through this section yet. See [What a new workspace starts with](/platform/upgrades#what-a-new-workspace-starts-with).
</Info>

To deploy a platform release:

1. Go to **Settings → Version Upgrades** and find the **Platform Components** section.
2. Open the release dropdown and select a release.
3. Select **Upgrade**.

While the deployment runs, the section shows **Upgrading…**. On success you'll see a confirmation banner; if a release fails or is rolled back, the section surfaces a banner and lists the affected release with details.

### Rolling back a platform release

If a platform release fails to deploy, it is rolled back automatically to the previous version - you don't need to do anything to recover. You can also move back to an earlier release yourself by selecting it in the dropdown and choosing **Upgrade**. See [Platform rollback](/platform/upgrades/rollbacks-and-recovery#platform-rollback).

<Info>
  Some platform releases are deployed automatically by the platform and are not shown in the dropdown for manual deployment. You only see releases you can deploy yourself.
</Info>

## See also

* [Rollbacks, failure modes, and recovery](/platform/upgrades/rollbacks-and-recovery) - how these rollouts behave and recover.
* [Status signals](/platform/upgrades/status-signals) - reading progress on each surface.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.