kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix inconsistency in documentation of default storageclass

This commit is contained in:
iheartNathan 2024-10-04 23:16:34 +01:00
parent ffe1d674f0
commit 4e3523c0a0
2 changed files with 13 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
content/en/docs/reference/access-authn-authz/admission-controllers.md
View File

@ -200,9 +200,12 @@ and automatically adds a default storage class to them.
This way, users that do not request any special storage class do not need to care about them at all and they
will get the default one.
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 does nothing when no default `StorageClass` exists. When more than one storage
class is marked as default, and you then create a `PersistentVolumeClaim` with no `storageClassName` set,
Kubernetes uses the most recently created default `StorageClass`.
When a `PersistentVolumeClaim` is created with a specified `volumeName`, it remains in a pending state
if the static volume's `storageClassName` does not match the `storageClassName` on the `PersistentVolumeClaim`
after any default StorageClass is applied to it.
This admission controller ignores any `PersistentVolumeClaim` updates; it acts only on creation.
See [persistent volume](/docs/concepts/storage/persistent-volumes/) documentation about persistent volume claims and

10
content/en/docs/tasks/administer-cluster/change-default-storage-class.md
View File

@ -73,9 +73,13 @@ for details about addon manager and how to disable individual addons.
kubectl patch storageclass gold -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
```
Please note that at most one StorageClass can be marked as default. If two
or more of them are marked as default, a `PersistentVolumeClaim` without
`storageClassName` explicitly specified cannot be created.
Please note you can have multiple `StorageClass` marked as default. If more
than one `StorageClass` is marked as default, a `PersistentVolumeClaim` without
an explicitly defined `storageClassName` will be created using the most recently
created default `StorageClass`.
When a `PersistentVolumeClaim` is created with a specified `volumeName`, it remains
in a pending state if the static volume's `storageClassName` does not match the
`StorageClass` on the `PersistentVolumeClaim`.
1. Verify that your chosen StorageClass is default: