Anyscale platform release notes - June 2026
Anyscale platform release notes - June 2026
Use this page to learn about new features and improvements to the Anyscale platform released in June 2026, including the Anyscale console, CLI, and SDK.
To learn about new features added as part of Ray releases, see Ray release highlights.
Anyscale CLI version 0.26.103 released
June 11, 2026
A new version of the Anyscale CLI and SDK is now available. See Version 0.26.103 release notes.
Anyscale operator for Kubernetes version 1.7.0 released
June 3, 2026
Anyscale has released version 1.7.0 of the Anyscale operator for Kubernetes. This release is backward-compatible and recommended for all users. See the Anyscale operator GitHub page for release details.
- Readiness probe: The operator now exposes
/readyzon port8081, and the Helm Deployment configures a matchingreadinessProbe.helm install --waitandhelm upgrade --waitno longer return success while the operator is still starting up or crash-looping. - Instance-type validation hook: A new pre-install and pre-upgrade Helm hook validates the planned instance-types ConfigMap against the control plane and fails the release on invalid types. Set
workloads.instanceTypes.validationHook.enabledtofalsewhen the control plane isn't reachable at install time. See Instance types. - Declarative-only setup fix: Fixed a bug where operator setups without instance types failed at startup.
Anyscale on Azure is now in Public Preview
June 2, 2026
Anyscale on Azure is now in Public Preview, a native integration with Azure that runs on Azure Kubernetes Service. The Anyscale control plane is hosted in Azure, and you manage your clouds, deployments, and monitoring from the Azure portal. For setup, architecture, networking, identity, and supported regions, see the Anyscale on Azure documentation on Microsoft Learn. For troubleshooting, see Anyscale on Azure knowledge base.
Mount EBS volumes to the head node on AWS (Beta)
June 1, 2026
You can now attach an existing AWS Elastic Block Store (EBS) volume to a cluster's head node and have Anyscale mount it into the Ray container at a path you choose. Use it to persist head-node-only data across cluster restarts, such as a Bazel or Docker build cache. You create and manage the volume, and the mount runs on AWS clouds backed by virtual machines. See Mount an EBS volume to the head node.