Skip to content
Permalink
Browse files

BlockVolume is no longer in alpha (#18167)

* BlockVolume is no longer alpha

Signed-off-by: dulltz <isrgnoe@gmail.com>

* Apply comment

#18167 (comment)

Co-Authored-By: Tim Bannister <tim@scalefactory.com>

* Apply comment

#18167 (comment)

* Apply comment

#18167 (review)
Signed-off-by: dulltz <isrgnoe@gmail.com>

Co-authored-by: Tim Bannister <tim@scalefactory.com>
  • Loading branch information
2 people authored and k8s-ci-robot committed Dec 23, 2019
1 parent d5966ba commit 296695d72937eec6134b50ce2bf28f7a20c13c1b
Showing with 2 additions and 4 deletions.
  1. +2 −4 content/en/docs/concepts/storage/volumes.md
@@ -657,7 +657,6 @@ metadata:
spec:
capacity:
storage: 100Gi
# volumeMode field requires BlockVolume Alpha feature gate to be enabled.
volumeMode: Filesystem
accessModes:
- ReadWriteOnce
@@ -679,9 +678,8 @@ PersistentVolume `nodeAffinity` is required when using local volumes. It enables
the Kubernetes scheduler to correctly schedule Pods using local volumes to the
correct node.

PersistentVolume `volumeMode` can now be set to "Block" (instead of the default
value "Filesystem") to expose the local volume as a raw block device. The
`volumeMode` field requires `BlockVolume` Alpha feature gate to be enabled.
PersistentVolume `volumeMode` can be set to "Block" (instead of the default
value "Filesystem") to expose the local volume as a raw block device.

When using local volumes, it is recommended to create a StorageClass with
`volumeBindingMode` set to `WaitForFirstConsumer`. See the

0 comments on commit 296695d

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