Update content/en/blog/_posts/2025-09-01-volume-attributes-class-ga/index.md

Co-authored-by: Agustina Barbetta <[email protected]>

Author: sunnylovestiramisu

content/en/blog/_posts/2025-09-01-volume-attributes-class-ga/index.md

@@ -1,20 +1,20 @@
 ---
 layout: blog
 title: "Kubernetes v1.34: VolumeAttributesClass for Volume Modification GA"
-date: 2025-0X-XX
+draft: true
 slug: kubernetes-v1-34-volume-attributes-class
 author: >
   Sunny Song (Google)
 ---
 
-The VolumeAttributesClass API, which empowers users to dynamically modify volume attributes, has officially graduated to General Availability (GA) in Kubernetes 1.34. This marks a significant milestone, providing a robust and stable way to tune your persistent storage directly within Kubernetes.
+The VolumeAttributesClass API, which empowers users to dynamically modify volume attributes, has officially graduated to General Availability (GA) in Kubernetes v1.34. This marks a significant milestone, providing a robust and stable way to tune your persistent storage directly within Kubernetes.
 
 
 ## What is VolumeAttributesClass?
 
 At its core, VolumeAttributesClass is a cluster-scoped resource that defines a set of mutable parameters for a volume. Think of it as a "profile" for your storage, allowing cluster administrators to expose different quality-of-service (QoS) levels or performance tiers.
 
-Users can then specify a volumeAttributesClassName in their PersistentVolumeClaim (PVC) to indicate which class of attributes they desire. The magic happens through the Container Storage Interface (CSI): when a PVC referencing a VolumeAttributesClass is updated, the associated CSI driver interacts with the underlying storage system to apply the specified changes to the volume.
+Users can then specify a `volumeAttributesClassName` in their PersistentVolumeClaim (PVC) to indicate which class of attributes they desire. The magic happens through the Container Storage Interface (CSI): when a PVC referencing a VolumeAttributesClass is updated, the associated CSI driver interacts with the underlying storage system to apply the specified changes to the volume.
 
 This means you can now:
 
@@ -27,16 +27,16 @@ This means you can now:
 
 There are two major enhancements from beta.
 
-### Cancel Support from Infeasible Errors
+### Cancel support from infeasible errors
 
 To improve resilience and user experience, the GA release introduces explicit cancel support when a requested volume modification becomes infeasible. If the underlying storage system or CSI driver indicates that the requested changes cannot be applied (e.g., due to invalid arguments), users can cancel the operation and revert the volume to its previous stable configuration, preventing the volume from being left in an inconsistent state.
 
 
-### Quota Support Based on Scope
+### Quota support based on scope
 
 While VolumeAttributesClass doesn't add a new quota type, the Kubernetes control plane can be configured to enforce quotas on PersistentVolumeClaims that reference a specific VolumeAttributesClass.
 
-This is achieved by using the scopeSelector field in a ResourceQuota to target PVCs that have spec.volumeAttributesClassName set to a particular VolumeAttributesClass name. Please see more details [here]( https://kubernetes.io/docs/concepts/policy/resource-quotas/#resource-quota-per-volumeattributesclass).
+This is achieved by using the `scopeSelector` field in a ResourceQuota to target PVCs that have `.spec.volumeAttributesClassName` set to a particular VolumeAttributesClass name. Please see more details [here]( https://kubernetes.io/docs/concepts/policy/resource-quotas/#resource-quota-per-volumeattributesclass).
 
 
 ## Drivers support VolumeAttributesClass