Skip to content

OSDOCS-17810: clarify VAC support for dynamic PVC performance updates #105668

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
jseseCCS wants to merge 1 commit into
base: enterprise-4.21
Choose a base branch
from
Open

OSDOCS-17810: clarify VAC support for dynamic PVC performance updates #105668

jseseCCS wants to merge 1 commit into from
+2 −0

Conversation

@jseseCCS
Copy link
Contributor

@jseseCCS jseseCCS commented Jan 29, 2026

This PR clarifies that starting in OpenShift Container Platform 4.21, a VolumeAttributesClass can be assigned to an existing persistent volume claim to adjust storage performance characteristics such as IOPS or throughput without reprovisioning.

Applies to OpenShift Container Platform 4.21 only.

Version(s): OpenShift Container Platform 4.21

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

@openshift-ci openshift-ci bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 29, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 29, 2026

Hi @jseseCCS. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@jseseCCS
Copy link
Contributor Author

jseseCCS commented Jan 29, 2026

@cajieh quick accuracy check please:
This PR clarifies that starting in OpenShift Container Platform 4.21, a VolumeAttributesClass can be applied to an existing PVC to adjust performance without reprovisioning. Can you confirm this statement is correct as written?

@jseseCCS jseseCCS changed the title [OSDOCS-17810]: clarify VAC support for dynamic PVC performance updates OSDOCS-17810: clarify VAC support for dynamic PVC performance updates Jan 29, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 29, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 29, 2026 •
edited by openshift-ci bot
Loading

@jseseCCS: This pull request references OSDOCS-17810 which is a valid jira issue.

Details

In response to this:

This PR clarifies that starting in OpenShift Container Platform 4.21, a VolumeAttributesClass can be assigned to an existing persistent volume claim to adjust storage performance characteristics such as IOPS or throughput without reprovisioning.

Applies to OpenShift Container Platform 4.21 only.

Version(s): OpenShift Container Platform 4.21

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

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 openshift-eng/jira-lifecycle-plugin repository.

cajieh
cajieh reviewed Jan 29, 2026
View reviewed changes
modules/storage-persistent-storage-pvc-volumeattributesclass.adoc
Volume Attributes Classes provide a way for administrators to describe "classes" of storage they offer. These different classes can correspond to different quality-of-service levels. You can then apply Volume Attributes Classes to a persistent volume claim (PVC). If needed, you can apply new Volume Attributes Classes that become available in the cluster to the PVC.

In {product-title} 4.21, you can assign a VolumeAttributesClass to an existing persistent volume claim to modify storage performance characteristics such as IOPS or throughput. This update does not require volume reprovisioning or application downtime and allows on-demand performance tuning for supported storage providers.

Copy link
Contributor

@cajieh cajieh Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! I’m wondering if the word 'existing' is necessary, since a VAC can also be applied during the initial provisioning of a PVC. I am copying @gnufied @gcharot for their thoughts.

Copy link
Contributor Author

@jseseCCS jseseCCS Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

absolutely right. i'll remove and resend your way. give me about 1 hour. thank you, @cajieh!

@jseseCCS jseseCCS force-pushed the OSDOCS-17810-vac-docs branch from b2aa363 to 69afb38 Compare January 29, 2026 20:51
@jseseCCS
Copy link
Contributor Author

jseseCCS commented Jan 29, 2026

@cajieh change made. if you don't object, I'm gonna ask @yapei to give us a QE review here? since merge freeze is in fewer than 24 hours. is that ok?

/assign @yapei if I may?

@jseseCCS
Copy link
Contributor Author

jseseCCS commented Jan 29, 2026

/assign @yapei

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@cajieh cajieh cajieh left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@yapei yapei

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@jseseCCS @openshift-ci-robot @cajieh @yapei