Breaking: The Kubernetes project has officially promoted Volume Group Snapshots to General Availability (GA) in the v1.36 release, marking a major milestone for stateful application portability. The feature, which enables crash-consistent snapshots across multiple persistent volumes, is now ready for production workloads.
“This GA release validates years of community effort to give users a reliable, standardized way to protect multi-volume applications,” said a Kubernetes SIG Storage representative. “Volume Group Snapshots eliminate the risk of inconsistent recovery points that plagued sequential snapshotting.”
Background
The feature debuted as alpha in Kubernetes v1.27, moved to beta in v1.32, and underwent a second beta in v1.34. Now, with v1.36, it achieves GA status—meaning the APIs are stable and backward-compatible.
Volume Group Snapshots rely on three new API kinds: VolumeGroupSnapshot, VolumeGroupSnapshotContent, and VolumeGroupClass. These allow users to define a group of PersistentVolumeClaim objects using label selectors, then take a point-in-time snapshot of all volumes in that group.
How It Works
A group snapshot represents copies made from multiple volumes at the exact same moment, ensuring write-order consistency. This is critical for applications that spread data across volumes—for example, a database storing data on one volume and logs on another.
“Restoring from individual snapshots taken at different times would corrupt the application,” explained a storage engineer involved in the feature design. “Group Snapshots guarantee that all volumes are in a consistent state, as if the entire application was paused simultaneously.”
The feature is supported only for CSI (Container Storage Interface) drivers that implement the GroupSnapshot capability. Users must also have the snapshot controller and a compatible CSI driver deployed.
Why This Matters
Previously, achieving crash consistency required application quiescence followed by sequential snapshots—a process that was time-consuming and sometimes impossible. Volume Group Snapshots eliminate that manual step.
“This is a game-changer for high-availability stateful workloads,” said a Kubernetes contributor from a major cloud provider. “Enterprises can now automate backup policies for complex, multi-volume applications without worrying about consistency gaps.”
What This Means
With GA, Volume Group Snapshots are ready for use in production pipelines. Users can create, restore, and manage group snapshots through kubectl or automation tools like Kasten, Velero, and custom controllers.
The APIs also enable new capabilities: restoring a group of snapshots to new volumes (rehydrate) or rolling back existing volumes to a prior state. This is particularly useful for disaster recovery and CI/CD testing.
“We expect rapid adoption now that the APIs are stable,” the SIG representative added. “The storage ecosystem will build richer integrations around group-level policies.”
What’s Next
The Kubernetes community is already exploring enhancements, including support for application-level quiescence hooks and orchestration across CSI drivers. For now, users should ensure their CSI drivers and snapshot controllers are updated to leverage GA.
Detailed documentation is available in the Kubernetes Volume Group Snapshots concept page. The feature’s API reference is also included in the v1.36 API documentation.
This is breaking news. More details to follow.