OSDOCS-15770#Vol Attribute Classes TP->GA

[lpettyjo]

Version(s): 4.21+

Issue: https://issues.redhat.com/browse/OSDOCS-15770

Link to docs preview: https://103425--ocpdocs-pr.netlify.app/openshift-enterprise/latest/storage/understanding-persistent-storage.html#storage-persistent-storage-pvc-volumeattributesclass_understanding-persistent-storage

QE review:

• QE has approved this change.

Additional information:

PTAL: @dfajmon @gcharot @radeore

[ocpdocs-previewbot]

🤖 Tue Jan 06 20:31:42 - Prow CI generated the docs preview:

https://103425--ocpdocs-pr.netlify.app/openshift-dedicated/latest/storage/understanding-persistent-storage.html
https://103425--ocpdocs-pr.netlify.app/openshift-enterprise/latest/storage/understanding-persistent-storage.html
https://103425--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/storage/understanding-persistent-storage.html
https://103425--ocpdocs-pr.netlify.app/openshift-rosa/latest/storage/understanding-persistent-storage.html

[dfajmon]

changes since TP

Parameter Definition and Update Behavior

Customers must verify supported parameters with their storage provider and SHOULD explicitly declare all parameters in every VolumeAttributesClass (VAC) definition.

WARNING

Updating a PVC to use a different VAC functions as a patch operation, not a replacement. If the new VAC does not define a specific parameter that existed in the previous VAC, the PVC retains the old value. To prevent unintended configuration inheritance, ensure the target VAC includes all parameters found in the source VAC.

New Metric: Parameter Mismatch

A new metric, openshift_cluster_storage_vac_mismatch_parameters, helps identify inconsistent parameter sets that could lead to the persistence issues described above.

0: All VACs define the same set of parameters.

1: Mismatch detected. At least one VAC defines a different set of parameters than the others.

Update Frequency & Delays

While users can modify the VAC on a PVC at any time, rapid, successive updates to the same volume may trigger a cooldown period.

If a VAC is changed multiple times in a short duration, the underlying storage provider may enforce a delay. This can result in a wait time of several hours before the most recent VAC change is fully reconciled on the disk.

[lpettyjo]

PTAL @dfajmon I've addressed your comments. Thanks!

[openshift-ci]

@lpettyjo: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[dfajmon]

Nicely written!
LGTM