From b4ec63b39a4cd23f96b274c77a36366690e58f05 Mon Sep 17 00:00:00 2001 From: Hemant Kumar Date: Thu, 21 Apr 2022 13:46:04 -0400 Subject: [PATCH] Update content/en/blog/_posts/2022-04-18-volume-expansion-ga.md Co-authored-by: Tim Bannister --- content/en/blog/_posts/2022-04-18-volume-expansion-ga.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2022-04-18-volume-expansion-ga.md b/content/en/blog/_posts/2022-04-18-volume-expansion-ga.md index 9978687329..ea4c9947ba 100644 --- a/content/en/blog/_posts/2022-04-18-volume-expansion-ga.md +++ b/content/en/blog/_posts/2022-04-18-volume-expansion-ga.md @@ -55,7 +55,8 @@ Please refer to volume expansion documentation for intree volume types which sup In general to provide some degree of control over volumes that can be expanded, only dynamically provisioned PVCs whose storage class has `allowVolumeExpansion` parameter set to `true` are expandable. -A Kubernetes admin must edit storage class object and set `allowVolumeExpansion` field to true. For example: +A Kubernetes cluster administrator must edit the appropriate StorageClass object and set +the `allowVolumeExpansion` field to `true`. For example: ``` apiVersion: storage.k8s.io/v1