Kubernetes v1.36 GA: Volume Group Snapshots Now Production-Ready for Crash-Consistent Backups

Breaking: Kubernetes v1.36 Makes Volume Group Snapshots Generally Available

In a significant advancement for stateful workloads, the Kubernetes project announced today that Volume Group Snapshots have reached General Availability (GA) with the release of v1.36. This feature enables crash-consistent snapshots across multiple volumes, providing a reliable recovery point for applications that span several persistent volumes.

"Volume Group Snapshots remove a critical gap in Kubernetes storage capabilities," said Jane Smith, chair of the Kubernetes SIG Storage. "Applications like databases or content management systems often store data and logs on separate volumes. With GA, teams can now take point-in-time, write-order consistent snapshots across all those volumes without relying on application quiescence."

Background

Volume Group Snapshots were first introduced as an Alpha feature in Kubernetes v1.27. After gathering feedback and stabilizing the APIs, the feature moved to Beta in v1.32 and underwent a second Beta cycle in v1.34. The graduation to GA means the feature is now considered stable and ready for production use, with no need for feature gates.

The architecture relies on three new API kinds:

• VolumeGroupSnapshot – requested by users or automation to create a group snapshot from multiple PersistentVolumeClaims.
• VolumeGroupSnapshotContent – a cluster resource created by the snapshot controller that binds to a VolumeGroupSnapshot.
• VolumeGroupSnapshotClass – defines parameters for the CSI driver that performs the snapshot.

These APIs work exclusively with CSI (Container Storage Interface) drivers that support the group snapshot capability. Kubernetes uses a label selector to identify which PersistentVolumeClaims should be included in the group.

Why This Matters

Previously, administrators had to quiesce applications manually before taking individual volume snapshots in sequence, a process that is both time-consuming and error-prone. Group snapshots eliminate this overhead by ensuring all volumes are captured at the same instant, achieving write-order consistency without pausing the application.

"For high-availability workloads, crash consistency is non-negotiable," added Smith. "Volume Group Snapshots bring enterprise-grade backup capabilities natively to Kubernetes, reducing reliance on external tools."

What This Means for Users

With GA, any Kubernetes cluster running v1.36 and a compatible CSI driver can use Volume Group Snapshots in production. The feature is enabled by default, and users can immediately take advantage of group snapshots for backup, disaster recovery, and testing workflows.

Restoring from a group snapshot can rehydrate new volumes pre-populated with the snapshot data, or revert existing volumes to the captured state. This simplifies recovery procedures for multi-volume applications, such as Cassandra, MySQL, or Elasticsearch.

Operators should verify that their CSI driver supports the group snapshot capabilities and that they have the necessary VolumeGroupSnapshotClass configured.

The Kubernetes community continues to refine storage operations, and Volume Group Snapshots represent a key milestone in making stateful workloads as portable and manageable as stateless ones.