From 5aca46b3d0c20e98a6bbd662e800a8d68ac9526e Mon Sep 17 00:00:00 2001 From: Tamilselvan Date: Wed, 14 Feb 2024 09:39:30 +0530 Subject: [PATCH] Update content/en/docs/concepts/storage/dynamic-provisioning.md Co-authored-by: Sean McGinnis --- content/en/docs/concepts/storage/dynamic-provisioning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/storage/dynamic-provisioning.md b/content/en/docs/concepts/storage/dynamic-provisioning.md index afefe2a590788..903945f12b6e5 100644 --- a/content/en/docs/concepts/storage/dynamic-provisioning.md +++ b/content/en/docs/concepts/storage/dynamic-provisioning.md @@ -119,7 +119,7 @@ When a default `StorageClass` exists in a cluster and a user creates a `DefaultStorageClass` admission controller automatically adds the `storageClassName` field pointing to the default storage class. -Note that If you set the `storageclass.kubernetes.io/is-default-class` +Note that if you set the `storageclass.kubernetes.io/is-default-class` annotation to true on more than one StorageClass in your cluster, and you then create a `PersistentVolumeClaim` with no `storageClassName` set, Kubernetes uses the most recently created default StorageClass.