Skip to content
Permalink
Browse files

solved for issue #17853 (#17872)

* solved for issue #17853

* updated file as per the suggestion
  • Loading branch information
Vageesha17 authored and k8s-ci-robot committed Nov 29, 2019
1 parent 5822f8a commit a02dc2d616c2e0b30df735dd32b4599c1c14a41b
Showing with 5 additions and 6 deletions.
  1. +5 −6 content/en/docs/concepts/storage/persistent-volumes.md
@@ -722,12 +722,11 @@ and need persistent storage, it is recommended that you use the following patter
`persistentVolumeClaim.storageClassName` field.
This will cause the PVC to match the right storage
class if the cluster has StorageClasses enabled by the admin.
- If the user does not provide a storage class name, leave the
`persistentVolumeClaim.storageClassName` field as nil.
- This will cause a PV to be automatically provisioned for the user with
the default StorageClass in the cluster. Many cluster environments have
a default StorageClass installed, or administrators can create their own
default StorageClass.
- If the user does not provide a storage class name, leave the
`persistentVolumeClaim.storageClassName` field as nil. This will cause a
PV to be automatically provisioned for the user with the default StorageClass
in the cluster. Many cluster environments have a default StorageClass installed,
or administrators can create their own default StorageClass.
- In your tooling, watch for PVCs that are not getting bound after some time
and surface this to the user, as this may indicate that the cluster has no
dynamic storage support (in which case the user should create a matching PV)

0 comments on commit a02dc2d

Please sign in to comment.
You can’t perform that action at this time.