This page documents production updates to Cluster Director. Check this page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.
You can see the latest product updates for all of Google Cloud on the
[Google Cloud](https://docs.cloud.google.com/release-notes.md.txt) page, browse and filter all release notes in the
[Google Cloud console](https://console.cloud.google.com/release-notes),
or programmatically access release notes in
[BigQuery](https://console.cloud.google.com/bigquery?p=bigquery-public-data&d=google_cloud_release_notes&t=release_notes&page=table).

## November 11, 2026

Feature **Preview** : You can create and manage clusters in Cluster Director that
provision compute nodes by using Compute Engine managed instance groups (MIGs)
instead of Slurm. Managed compute clusters automate VPC and RDMA
network setup, shared storage mounting, and topology-aware placement policies so
that you can run distributed workloads directly over SSH or integrate your own
orchestrator. For more information, see
[Managed compute orchestration in Cluster Director](https://docs.cloud.google.com/cluster-director/docs/managed-compute-orchestration.md.txt).

## November 10, 2026

Feature **Generally available** : Cluster Director supports the Doha, Qatar
(`me-central1`) region. For more information, see
[Cluster Director locations](https://docs.cloud.google.com/cluster-director/docs/locations.md.txt).

## November 03, 2026

Feature **Preview** : You can create Slurm clusters with TPU7x, TPU v6e, and TPU v5p
virtual machine (VM) instances. Use TPU VMs to run large-scale artificial
intelligence (AI) and machine learning (ML) training and inference workloads.
For more information, see
[Supported TPU machines for Cluster Director](https://docs.cloud.google.com/cluster-director/docs/tpu-machines.md.txt).

## October 21, 2026

Feature **Generally available** : You can use the C4A machine series for login nodes in
clusters that use the A4X Max or A4X machine series for compute nodes. This
configuration provides a consistent Arm-based architecture across compute and
login nodes in your cluster. For more information, see
[C4A machine series](https://docs.cloud.google.com/cluster-director/docs/cpu-machines.md.txt#c4a-series).

## October 13, 2026

Feature **Generally available** : You can use the
`a3-h100-ubuntu-2204-amd64-nvidia-580-slurm-2505-v20260805` OS image family for
VMs that use the A3 Mega machine type. This Ubuntu 22.04 LTS image family is the
default for A3 Mega VMs, uses Slurm version 25.05, and includes NVIDIA driver
580 with CUDA Toolkit 13. For more information, see
[Supported OS images for Cluster Director](https://docs.cloud.google.com/cluster-director/docs/os-images.md.txt).

## October 12, 2026

Feature **Generally available**: You can use the following Ubuntu 24.04 LTS OS image
families for the compute and login nodes in your cluster:

- **A4X** : `a4x-ubuntu-2404-arm64-nvidia-595-slurm-2605-v20260903`
- **A4, A3 Ultra, and N2** : `common-ubuntu-2404-amd64-nvidia-595-slurm-2605-v20260903`
- **A3 Mega** : `a3-h100-ubuntu-2404-amd64-nvidia-595-slurm-2605-v20260903`

These image families use Slurm version 26.05 and include NVIDIA driver 595 with
CUDA Toolkit 13. For more information, see
[Supported OS images for Cluster Director](https://docs.cloud.google.com/cluster-director/docs/os-images.md.txt).

## October 06, 2026

Feature **Generally available** : When you reserve compute resources for your cluster
through your account team, you can include a Hyperdisk pool in
the same request or in a subsequent request. This option helps ensure that your
artificial intelligence (AI) and machine learning (ML) workloads have the
storage resources that they require close to your compute nodes. For more
information, see
[Reserve capacity through your account team](https://docs.cloud.google.com/cluster-director/docs/reserve-capacity.md.txt).

## October 01, 2026

Feature **Generally available** : When you create or modify a cluster, you can specify
custom Slurm settings. You can apply these settings across a cluster, for
specific partitions, or for compute nodes in specific nodesets. These settings
let you customize workload scheduling, job preemption, queue priority, and
resource limits based on your workload requirements. For more information, see
[Supported Slurm settings in Cluster Director](https://docs.cloud.google.com/cluster-director/docs/slurm-settings.md.txt).

## September 30, 2026

Feature **Generally available** : When you create a cluster by using the
gcloud CLI or REST API, you can specify the Slurm version that the
controller node uses. This setting helps you align software versions with your
workload requirements. For more information, see
[Slurm controller versions in Cluster Director](https://docs.cloud.google.com/cluster-director/docs/slurm-controller-versions.md.txt).
Feature **Generally available** : You can use existing storage pools or
Hyperdisk Exapools with Hyperdisk Balanced disks
for the boot disks in your compute and login nodes. Storage pools help you
optimize costs because they share capacity and performance across boot disks.
For more information, see
[Supported storage services for Cluster Director](https://docs.cloud.google.com/cluster-director/docs/storage.md.txt).

## September 22, 2026

Feature **Generally available** : When you create a cluster, you can specify the Rapid
storage class for the Cloud Storage buckets that you create with the cluster.
The Rapid storage class provides low latency and high throughput, which is ideal
for artificial intelligence (AI) and machine learning (ML) workloads. For more
information, see
[Supported storage services for Cluster Director](https://docs.cloud.google.com/cluster-director/docs/storage.md.txt).

## September 09, 2026

Feature **Generally available** : You can use Managed Lustre instances
that use the Dynamic tier in your clusters. The Dynamic tier provides
cost-effective storage for large datasets. For more information, see
[Supported storage services for Cluster Director](https://docs.cloud.google.com/cluster-director/docs/storage.md.txt).

## September 04, 2026

Security Google addressed a security vulnerability (CVE-2026-65107) in the Slurm `sbcast`
tool that affects Cluster Director. For more information, see the
[security bulletin](https://docs.cloud.google.com/cluster-director/docs/security-bulletins.md.txt#gcp-2026-060).

## August 31, 2026

Feature **Generally available** : You can use prebuilt Cloud Monitoring dashboards to
monitor CPU, GPU, and memory usage, node health, and queue status for your Slurm
workloads. This information helps you troubleshoot job queue delays, identify
performance bottlenecks, and balance compute capacity. For more information, see
[Monitor cluster performance with prebuilt dashboards](https://docs.cloud.google.com/cluster-director/docs/monitor/dashboards.md.txt).

## August 25, 2026

Change If you create a VM by using an auto-created reservation for a future reservation
in calendar mode, then Cluster Director deletes the VM when the
reservation reaches its end time. If you specify to stop the VM when the
reservation reaches its end time, then Cluster Director ignores this
configuration. For more information, see
[Use future reservations in calendar mode](https://docs.cloud.google.com/cluster-director/docs/choose-consumption-option.md.txt#calendar-mode).

## July 27, 2026

Feature **Generally available** : You can use Cluster Director built-in metrics for
Slurm to monitor resource usage for your clusters and their nodes. Create custom
dashboards and alerting policies in Cloud Monitoring with these built-in
metrics to identify bottlenecks, optimize resource consumption, and troubleshoot
errors. For more information, see
[Monitor clusters with custom dashboards or alerts](https://docs.cloud.google.com/cluster-director/docs/monitor/custom-dashboards.md.txt).

## June 25, 2026

Change Documentation has been added to explain the states that a cluster node goes
through in its lifecycle. Understanding these states helps you manage costs
and resources, minimize disruptions, and troubleshoot errors. For more
information, see [Node lifecycle](https://docs.cloud.google.com/cluster-director/docs/manage/node-lifecycle.md.txt).

## June 23, 2026

Feature **Preview** : You can use Gemini in the Google Cloud console as
an AI-powered interface to evaluate hardware options, estimate deployment costs,
and view recommended configurations for your clusters. Interacting with
Gemini helps you reach an optimal configuration for your cluster
before you create or modify it. For more information, see
[Design and optimize your cluster with Gemini](https://docs.cloud.google.com/cluster-director/docs/create/design-with-gemini.md.txt).

## June 19, 2026

Feature **Generally available** : You can temporarily mount Cloud Storage buckets on
cluster nodes for the duration of a Slurm job. This action helps you read and
write data directly to Cloud Storage without permanently adding storage
resources to your cluster. For more information, see
[Mount Cloud Storage buckets for specific jobs](https://docs.cloud.google.com/cluster-director/docs/workloads/mount-buckets.md.txt).

## June 18, 2026

Feature **Generally available**: Cluster Director supports the following regions:

- **APAC**:

  - Tokyo, Japan (`asia-northeast1`)

  - Delhi, India (`asia-south2`)

- **North America**:

  - Los Angeles, USA (`us-west2`)

  - Salt Lake City, USA (`us-west3`)

For more information, see
[Cluster Director locations](https://docs.cloud.google.com/cluster-director/docs/locations.md.txt).

## June 15, 2026

Feature **Preview** : Before you create Spot VMs in a cluster partition, you can
view the real-time availability, estimated uptime, historical preemption rate,
and pricing for a specific machine type and location. This information helps you
maximize the chances of successfully creating Spot VMs and choose
the configuration that best fits your workload needs and budget. For more
information, see
[Use Spot](https://docs.cloud.google.com/cluster-director/docs/choose-consumption-option.md.txt#spot).

## June 02, 2026

Change Documentation has been added to explain the lifecycle for the supported OS image
families in Cluster Director. For more information, see
[Image family lifecycle](https://docs.cloud.google.com/cluster-director/docs/os-images.md.txt#lifecycle).

## June 01, 2026

Change Documentation has been added to list the cluster properties that restart or
recreate nodes when you modify a cluster. This information helps you minimize
disruptions to your workload. For more information, see
[Modify a cluster](https://docs.cloud.google.com/cluster-director/docs/manage/modify-cluster.md.txt).
Feature **Generally available** : Every two minutes, Slurm runs a background health check
on the GPUs attached to your compute nodes to detect errors. If the script finds
an error, then it logs the error to the compute node's system logs. This check
helps you monitor your GPUs without draining your nodes. For more information,
see
[Key Slurm capabilities](https://docs.cloud.google.com/cluster-director/docs/slurm-orchestration.md.txt#capabilities).

## May 15, 2026

Change Documentation has been added to list the available OS image families in
Cluster Director, their end of support (EOS) dates, and their patch
release notes. For more information, see
[Image family release notes](https://docs.cloud.google.com/cluster-director/docs/image-family-release-notes.md.txt).

## December 17, 2025

Announcement [Cluster Director](https://docs.cloud.google.com/cluster-director/docs.md.txt) is generally available
([GA](https://docs.cloud.google.com/products#product-launch-stages)).
Issue Cluster operations fail if you use a gcloud CLI version earlier than
550.0.0. To resolve this issue, update the gcloud CLI to version
550.0.0 or later. For more information, see
[Known issues](https://docs.cloud.google.com/cluster-director/docs/troubleshoot/known-issues.md.txt).