OSDOCS-16945# CQA work Stor1 -- vol resize#106419
Conversation
lpettyjo
added
branch/enterprise-4.16
branch/enterprise-4.17
branch/enterprise-4.18
branch/enterprise-4.19
branch/enterprise-4.20
branch/enterprise-4.21
branch/enterprise-4.22
merge-review-needed
openshift-ci
Bot
added
the
size/M
|
@lpettyjo: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
dfitzmau
added
peer-review-in-progress
| Before you can expand persistent volumes, the `StorageClass` object must | ||
| have the `allowVolumeExpansion` field set to `true`. | ||
| [role="_abstract"] | ||
| Before you can expand persistent volumes, the `StorageClass` object must have the `allowVolumeExpansion` field set to `true`. |
There was a problem hiding this comment.
The "why" is missing for some of these abstracts. I use this NotebookLM to help with writing short descriptions,especially for ideas on how to capture the "how" and "why" of a short description.
To expand persistent volumes, set the
allowVolumeExpansionfield totruein theStorageClassobject. By setting this configuration, you can resize volumes to meet your storage requirements.
| ---- | ||
| <1> Setting this attribute to `true` allows PVCs to be | ||
| expanded after creation. | ||
| + |
There was a problem hiding this comment.
This callout renders like the previous steps:
Maybe ** would work better? Or follow the pattern of the callout from the other code block to keep things consistent.
| .Prerequisites | ||
|
|
||
| * The underlying CSI driver supports resize. See "CSI drivers supported by {product-title}" in the "Additional resources" section. | ||
| * The underlying CSI driver supports resize. |
There was a problem hiding this comment.
Consider keeping "For information..." line on the same line as the prereq.
|
|
||
| . Watch the `status.conditions` field of the PVC to see if the resize has completed. {product-title} adds the `Resizing` condition to the PVC during expansion, which is removed after expansion completes. | ||
| .Verification | ||
| To confirm that the resize is finished, look at the `status.conditions` field of the PVC . {product-title} adds the `Resizing` condition to the PVC during expansion, which is removed after expansion completes. |
There was a problem hiding this comment.
| To confirm that the resize is finished, look at the `status.conditions` field of the PVC . {product-title} adds the `Resizing` condition to the PVC during expansion, which is removed after expansion completes. | |
| * To confirm that the resize is finished, look at the `status.conditions` field of the PVC . {product-title} adds the `Resizing` condition to the PVC during expansion, which is removed after expansion completes. |
|
|
||
| ifdef::microshift[] | ||
| Expanding PVCs based on volume types that need file system resizing, such as GCE Persistent Disk volumes (gcePD), AWS Elastic Block Store EBS (EBS), and Cinder, is a two-step process. First, expand the volume objects in the cloud provider. Second, expand the file system on the node. | ||
| Expanding PVCs based on volume types that need file system resizing, such as Google Cloud Platform (GCP) persistent disk (PD), AWS Elastic Block Store EBS (EBS), and Cinder, is a two-step process. First, expand the volume objects in the cloud provider. Second, expand the file system on the node. |
There was a problem hiding this comment.
Google Cloud Platform (GCP) > Google Cloud
| ---- | ||
|
|
||
| . When the cloud provider object has finished resizing, the `PersistentVolume` object reflects the newly requested size in `PersistentVolume.Spec.Capacity`. At this point, you can create or recreate a new pod from the PVC to finish the file system resizing. Once the pod is running, the newly requested size is available and the `FileSystemResizePending` condition is removed from the PVC. | ||
| .Next steps |
There was a problem hiding this comment.
Usually the Vale check fails for next steps. If so, perhaps a new step could be added.
| = Expanding local volumes | ||
|
|
||
| [role="_abstract"] | ||
| You can manually expand persistent volumes (PVs) and persistent volume claims (PVCs) created by using the local storage operator (LSO). |
There was a problem hiding this comment.
| You can manually expand persistent volumes (PVs) and persistent volume claims (PVCs) created by using the local storage operator (LSO). | |
| You can manually expand persistent volumes (PVs) and persistent volume claims (PVCs) created by using the local storage operator (LSO). With this process, you can increase storage capacity for your workloads to meet changing application requirements. |
dfitzmau
removed
the
peer-review-in-progress
openshift-merge-robot
added
the
needs-rebase
|
PR needs rebase. DetailsInstructions 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. |
lpettyjo
changed the title
4 participants
Version(s): 4.16+
Issue: https://issues.redhat.com/browse/OSDOCS-16945
Link to docs preview: https://106419--ocpdocs-pr.netlify.app/openshift-enterprise/latest/storage/expanding-persistent-volumes.html
QE review:
Additional information: