From 4fcbbea71c871e1d16fb6b849107187450ad4bb4 Mon Sep 17 00:00:00 2001 From: Hemant Kumar Date: Mon, 25 Apr 2022 12:54:48 -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 | 2 +- 1 file changed, 1 insertion(+), 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 8f857244c3..d045cb4eca 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 @@ -83,7 +83,7 @@ his behaviour has been changed and Kubernetes tries its best to fulfil any resiz of whether the underlying PersistentVolume volume is online or offline. If your storage provider supports online expansion then no Pod restart should be necessary for volume expansion to finish. -### ## What’s next? +## Next steps Although Volume expansion is going GA with 1.24 - we are continously working to make it simpler for users of Kubernetes to expand their persistent volumes. Kubernetes 1.23 introduced feature `RecoverVolumeExpansionFailure` - so as users can themselves recover from volume expansion failures (usually recovering from volume expansion requires admin intervention) whenever possible. See - [Rcovering from volume expansion failure](/docs/concepts/storage/persistent-volumes/#recovering-from-failure-when-expanding-volumes) for more details.