Storage Classes - contradicting behavior statements

[dmytro-storozhuk]

The default Storage class behaviour in https://kubernetes.io/docs/concepts/storage/storage-classes/#default-storageclass says:

"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."

whereas, in the addmission controllers page (https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#defaultstorageclass) for controller that does this amendment:

"This admission controller does not do anything when no default storage class is configured. When more than one storage class is marked as default, it rejects any creation of PersistentVolumeClaim with an error and an administrator must revisit their StorageClass objects and mark only one as default. This admission controller ignores any PersistentVolumeClaim updates; it acts only on creation."

So, what is the correct one?

Thanks

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions 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.

[dmytro-storozhuk]

and one more place https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/#defaulting-behavior

"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."

[T-Lakshmi]

/sig storage

[dmytro-storozhuk]

The test on local minikube cluster (v.1.30.0) showed that PVC provisioned (BOUND state) with the latest "default" StorageClass assigned. So, the description of DefaultStorageClass is misleading.

[sftim]

Is this a duplicate of issue #42288?

[sftim]

/language en

[dmytro-storozhuk]

@sftim yes, it is a duplicate. The documentation hasn't been updated for a year

[sftim]

/close not-planned

There is an existing issue; help is welcome.

[k8s-ci-robot]

@sftim: Closing this issue, marking it as "Not Planned".

In response to this:

/close not-planned

There is an existing issue; help is welcome.

Instructions 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.

[iheartNathan]

/assign

[iheartNathan]

/unassign