From 13495193e10d5e6fe3530caa8d15886ceb5cbbed Mon Sep 17 00:00:00 2001 From: tamilselvan1102 Date: Tue, 30 Jan 2024 10:58:10 +0530 Subject: [PATCH 1/4] Information about default StorageClasses --- .../en/docs/concepts/storage/dynamic-provisioning.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/storage/dynamic-provisioning.md b/content/en/docs/concepts/storage/dynamic-provisioning.md index 54ab391d80..d2e6f8c75f 100644 --- a/content/en/docs/concepts/storage/dynamic-provisioning.md +++ b/content/en/docs/concepts/storage/dynamic-provisioning.md @@ -119,9 +119,13 @@ 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 there can be at most one *default* storage class on a cluster, or -a `PersistentVolumeClaim` without `storageClassName` explicitly specified cannot -be created. +Note that If you set the +[`storageclass.kubernetes.io/is-default-class`](/docs/reference/labels-annotations-taints/#ingressclass-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. + +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. ## Topology Awareness From f4399903165ca8729a434f2572e3e2b8395215d3 Mon Sep 17 00:00:00 2001 From: Tamilselvan Date: Tue, 30 Jan 2024 11:06:06 +0530 Subject: [PATCH 2/4] Information about default StorageClasses --- content/en/docs/concepts/storage/dynamic-provisioning.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/en/docs/concepts/storage/dynamic-provisioning.md b/content/en/docs/concepts/storage/dynamic-provisioning.md index d2e6f8c75f..1897656d9d 100644 --- a/content/en/docs/concepts/storage/dynamic-provisioning.md +++ b/content/en/docs/concepts/storage/dynamic-provisioning.md @@ -125,8 +125,6 @@ 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. -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. - ## Topology Awareness In [Multi-Zone](/docs/setup/best-practices/multiple-zones/) clusters, Pods can be spread across From df4e3e1c11bad696df726bac36e6b25048d17f6b Mon Sep 17 00:00:00 2001 From: Tamilselvan Date: Tue, 30 Jan 2024 11:13:19 +0530 Subject: [PATCH 3/4] Information about default StorageClasses --- content/en/docs/concepts/storage/dynamic-provisioning.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/docs/concepts/storage/dynamic-provisioning.md b/content/en/docs/concepts/storage/dynamic-provisioning.md index 1897656d9d..afefe2a590 100644 --- a/content/en/docs/concepts/storage/dynamic-provisioning.md +++ b/content/en/docs/concepts/storage/dynamic-provisioning.md @@ -119,8 +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`](/docs/reference/labels-annotations-taints/#ingressclass-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. From 5aca46b3d0c20e98a6bbd662e800a8d68ac9526e Mon Sep 17 00:00:00 2001 From: Tamilselvan Date: Wed, 14 Feb 2024 09:39:30 +0530 Subject: [PATCH 4/4] 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 afefe2a590..903945f12b 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.