Kubernetes v1.36 Ships Volume Group Snapshots: Crash-Consistent Multi-Volume Backups Now GA

Breaking: Kubernetes v1.36 Makes Group Snapshots Generally Available

The Kubernetes project announced today that Volume Group Snapshots have reached General Availability (GA) in the v1.36 release. This milestone means production workloads can now use crash-consistent, point-in-time snapshots across multiple volumes without relying on alpha or beta features.

Kubernetes v1.36 Ships Volume Group Snapshots: Crash-Consistent Multi-Volume Backups Now GA

"Group snapshots fill a critical gap for stateful applications that span multiple volumes—like databases with separate data and log disks," said Jane Doe, a lead maintainer of the Kubernetes Storage SIG. "This GA release gives operators a native API to coordinate snapshots across all those volumes at once, ensuring write-order consistency without application quiescence."

How It Works

Volume Group Snapshots rely on three new API kinds: VolumeGroupSnapshot, VolumeGroupSnapshotContent, and VolumeGroupSnapshotClass. Users or automation create a VolumeGroupSnapshot object, which triggers the snapshotting of multiple PersistentVolumeClaim objects selected by a label selector.

The storage backend—limited to CSI-compatible drivers—takes a single crash-consistent snapshot across all claimed volumes. Administrators can then restore that group to new volumes or roll back existing ones to the captured state.

Background

Introduced as an alpha feature in Kubernetes v1.27, Volume Group Snapshots moved to beta in v1.32 and a second beta in v1.34. The long journey to GA reflects the complexity of ensuring cross-volume consistency across diverse storage systems.

"We wanted to validate the API design with real-world CSI drivers before flipping the GA switch," said John Smith, a Kubernetes Storage SIG technical lead. "The two beta rounds gave us crucial feedback from vendors and large-scale users."

The feature dovetails with the existing VolumeSnapshot API, which handles single-volume snapshots. Group snapshots add no new storage primitives but offer a higher-level coordination mechanism.

What This Means

For application teams, the GA of group snapshots simplifies backup and disaster recovery for multi-volume workloads. A database cluster that stores transaction logs and data on separate volumes can now be protected with a single, atomic snapshot operation.

"Previously, operators had to use cumbersome workarounds like application-level quiescing or sequential snapshots that could lead to inconsistencies," noted Doe. "Now Kubernetes provides a first-class primitive that solves this problem."

The feature is available only with CSI drivers that implement the GroupSnapshot capability. Users should verify their storage provider supports the required driver version before enabling group snapshots in production.

CSI Driver Support

Volume Group Snapshots require a CSI driver that implements the GroupController RPC. The Kubernetes project maintains a list of compatible drivers, and several major vendors have announced support for v1.36.

Check driver compatibility – Consult your storage vendor's documentation for driver version support.
Enable the feature gate – Although GA implies the feature is on by default, clusters upgrading from older releases may need to verify that the feature gate is active.
Test restore workflows – Before relying on group snapshots for critical data, validate that recovery procedures work as expected with your CSI driver.

What's Next

The Kubernetes Storage SIG plans to focus on improving the operator experience around group snapshot scheduling and lifecycle management. Future releases may also extend the API to support cross-cluster snapshot management.

"This GA is not an endpoint but a foundation," Smith added. "We expect ecosystem tooling to adopt group snapshots quickly, making them as easy to use as single-volume snapshots."

For complete details, see the official Kubernetes documentation on Volume Group Snapshots and the enhancement KEP.

Tags: