OSDOCS-13351#Vol group snapshots TP -> GA

modules/persistent-storage-csi-drivers-supported.adoc

@@ -38,59 +38,54 @@ endif::openshift-rosa,openshift-rosa-hcp,openshift-aro[]
 .Supported CSI drivers and features in {product-title}
 [cols=",^v,^v,^v,^v,^v,^v,^v width="100%",options="header"]
 |===
-|CSI driver |CSI volume snapshots  |CSI volume group snapshots ^[1]^ |CSI cloning  |CSI resize |Inline ephemeral volumes |User namespaces
+|CSI driver |CSI volume snapshots  |CSI volume group snapshots |CSI cloning  |CSI resize |Inline ephemeral volumes |User namespaces
 |AWS EBS | ✅ |  |  | ✅| | ✅
 |AWS EFS |  |  |  |  | |
 ifndef::openshift-rosa,openshift-rosa-hcp[]
-|Google Compute Platform (GCP) persistent disk (PD)|  ✅|  |✅^[2]^ | ✅|  | ✅
+|Google Compute Platform (GCP) persistent disk (PD)|  ✅|  |✅^[1]^ | ✅|  | ✅
 |GCP Filestore | ✅ |  | | ✅| |
 endif::openshift-rosa,openshift-rosa-hcp[]
 ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
 |{ibm-power-server-name} Block |   |  |   | ✅ | | ✅
-|{ibm-cloud-name} Block | ✅^[3]^ |  |   | ✅^[3]^| | ✅
+|{ibm-cloud-name} Block | ✅^[2]^ |  |   | ✅^[2]^| | ✅
 endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
 |{lvms} | ✅ |  | ✅ | ✅ | | ✅
 ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
 |Microsoft Azure Disk | ✅ |  | ✅ | ✅| | ✅
 |Microsoft Azure Stack Hub | ✅ |  | ✅ | ✅| | ✅
 |Microsoft Azure File | ✅  |  | ✅ | ✅| ✅ |
 |OpenStack Cinder | ✅ |  | ✅ | ✅| | ✅
-|{rh-storage} | ✅ | ✅ | ✅ | ✅| | ✅ ^[4]^
+|{rh-storage} | ✅ | ✅ | ✅ | ✅| | ✅ ^[3]^
 |OpenStack Manila | ✅ |  |   | ✅  | |
 |CIFS/SMB |   |  | ✅  |   | |
-|VMware vSphere | ✅^[5]^ |  |   | ✅^[6]^| | ✅ ^[7]^
+|VMware vSphere | ✅^[4]^ |  |   | ✅^[5]^| | ✅ ^[6]^
 endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
 |===
 ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
 --
 1.
 
-:FeatureName: CSI volume group snapshots
-include::snippets/technology-preview.adoc[leveloffset=+1]
-
-2.
-
 Cloning is not supported on hyperdisk-balanced disks with storage pools.
 
-3.
+2.
 
 Does not support offline snapshots or resize. Volume must be attached to a running pod.
 
-4.
+3.
 
 RBD supports user namespaces; CephFS does not.
 
-5.
+4.
 
 * Requires VMware vSphere version 8.0 Update 1 or later, or VMware vSphere Foundation (VVF) 9, or VMware Cloud Foundation (VCF) 9, for both vCenter Server and ESXi.
 
 * Does not support fileshare volumes.
 
-6.
+5.
 
 Online expansion is supported from VMware vSphere version 8.0 Update 1 and later, or VVF 9, or VCF 9.
 
-7.
+6.
 
 File persistent volumes (PVs), such as vSAN file service, do not support user namespaces.
 

modules/persistent-storage-csi-group-snapshot-create-admin.adoc

@@ -11,15 +11,14 @@ Create a `VolumeGroupSnapshotClass` to define how volume group snapshots are pro
 
 .Prerequisites
 * Logged in to a running {product-title} cluster with administrator privileges.
-* Enabled this feature using feature gates. For information about how to use feature gates, see "Enabling features sets by using feature gates".
 
 .Procedure
 . Create a `VolumeGroupSnapshotClass` YAML file using the following example file:
 +
 .Example volume group snapshot class YAML file
 [source, yaml]
 ----
-apiVersion: groupsnapshot.storage.k8s.io/v1beta2
+apiVersion: groupsnapshot.storage.k8s.io/v1
 kind: VolumeGroupSnapshotClass
 metadata:
   name: csi-hostpath-groupsnapclass

modules/persistent-storage-csi-group-snapshots-create.adoc

@@ -13,7 +13,6 @@ When you create a `VolumeGroupSnapshot` object, {product-title} creates a volume
 
 .Prerequisites
 * Logged in to a running {product-title} cluster.
-* Enabled this feature using feature gates. For information about how to use feature gates, see "Enabling features sets by using feature gates".
 * The persistent volume claims (PVCs) that you want to group for the snapshot have been created using a CSI driver that supports `VolumeGroupSnapshot` objects.
 * A storage class to provision the storage back end.
 * Administrator has created the `VolumeGroupSnapshotClass` object.
@@ -71,7 +70,7 @@ In this example, you are labeling PVC "pvc-0" and "pvc-1" to belong to group "my
 .Example VolumeGroupSnapshot YAML file
 [source,yaml]
 ----
-apiVersion: groupsnapshot.storage.k8s.io/v1beta2
+apiVersion: groupsnapshot.storage.k8s.io/v1
 kind: VolumeGroupSnapshot
 metadata:
   name: <volume-group-snapshot-name>
@@ -109,7 +108,7 @@ metadata:
   name: snapshot-4dc1c53a29538b36e85003503a4bcac5dbde4cff59e81f1e3bb80b6c18c3fd03
   namespace: default
   ownerReferences:
-  - apiVersion: groupsnapshot.storage.k8s.io/v1beta2
+  - apiVersion: groupsnapshot.storage.k8s.io/v1
     kind: VolumeGroupSnapshot
     name: my-groupsnapshot
     uid: ba2d60c5-5082-4279-80c2-daa85f0af354

modules/persistent-storage-csi-group-snapshots-overview.adoc

@@ -9,10 +9,7 @@
 [role="_abstract"]
 Volume group snapshots capture point-in-time copies of multiple persistent volume claims using label selectors. Three API objects manage snapshots: VolumeGroupSnapshot, VolumeGroupSnapshotContent, and VolumeGroupSnapshotClass. 
 
-:FeatureName: CSI volume group snapshots
-include::snippets/technology-preview.adoc[leveloffset=+1]
-
-To use this Technology Preview feature, you must enable it by using feature gates. For information about using feature gates, see "Enabling features using feature gates". 
+Volume group snapshots need to be supported by the Container Storage Interface (CSI) driver. {rh-storage} supports volume group snapshots.
 
 Snapshot:: A snapshot represents the state of the storage volume in a cluster at a particular point in time. Volume snapshots can be used to provision a new volume. 
 
@@ -31,4 +28,4 @@ Created by the snapshot controller for a dynamically created volumeGroupSnapshot
 `VolumeGroupSnapshotClass`::
 Created by cluster administrators to describe how volume group snapshots should be created, including the driver information, the deletion policy, etc.
 
-These three API kinds are defined as `CustomResourceDefinitions` (CRDs). These CRDs must be installed in a {product-title} cluster for a CSI driver to support volume group snapshots.
+These three API kinds are defined as `CustomResourceDefinitions` (CRDs). These CRDs are installed by default in the {product-title} cluster so that CSI drivers can support volume group snapshots.

storage/container_storage_interface/persistent-storage-csi-group-snapshots.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-[role="_abstract"] 
+[role="_abstract"]
 Volume group snapshots capture point-in-time copies of multiple volumes simultaneously, gathering data across related volumes. This enables restoring multi-volume applications to a previous state or provisioning new volume sets with the same data for testing or development purposes.
 
 include::modules/persistent-storage-csi-group-snapshots-overview.adoc[leveloffset=+1]
@@ -27,5 +27,4 @@ include::modules/persistent-storage-csi-group-snapshots-restore.adoc[leveloffset
 [id="additional-resources_{context}"]
 == Additional resources
 * xref:../../storage/understanding-persistent-storage.adoc#persistent-volumes_understanding-persistent-storage[Understanding persistent volumes]
-* xref:../../nodes/clusters/nodes-cluster-enabling-features.adoc#nodes-cluster-enabling-features[Enabling features using feature gates]
-* xref:../../storage/container_storage_interface/persistent-storage-csi-snapshots.adoc#persistent-storage-csi-snapshots[CSI volume snapshots]
+* xref:../../storage/container_storage_interface/persistent-storage-csi-snapshots.adoc#persistent-storage-csi-snapshots[CSI volume snapshots]