Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update block device support for 1.11 #8895

Merged
merged 2 commits into from
Jun 6, 2018
Merged

Update block device support for 1.11 #8895

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c6b503f
Update block device support for 1.11
jsafrane Jun 4, 2018
79e20ac
Copyedits
Jun 6, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 18 additions & 8 deletions content/en/docs/concepts/storage/persistent-volumes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -221,7 +221,7 @@ resizing to take place. Also, file system resizing is only supported for followi
* AWSElasticBlockStore
* AzureFile
* AzureDisk
* FC (Fibre Channel)**
* FC (Fibre Channel)
* FlexVolume
* Flocker
* NFS
Expand All @@ -237,8 +237,6 @@ resizing to take place. Also, file system resizing is only supported for followi
* ScaleIO Volumes
* StorageOS

Raw Block Support exists for these plugins only.

## Persistent Volumes

Each PV contains a spec and status, which is the specification and status of the volume.
Expand Down Expand Up @@ -272,11 +270,11 @@ Currently, storage size is the only resource that can be set or requested. Futu

### Volume Mode

Prior to v1.9, the default behavior for all volume plugins was to create a filesystem on the persistent volume. With v1.9, the user can specify a `volumeMode` which will now support raw block devices in addition to file systems. Valid values for `volumeMode` are "Filesystem" or "Block". If left unspecified, `volumeMode` defaults to "Filesystem" internally. This is an optional API parameter.
{{< feature-state for_k8s_version="v1.9" state="alpha" >}}

{{< note >}}
**Note:** This feature is alpha in v1.9 and may change in the future.
{{< /note >}}
To enable this feature in v1.9, the cluster administrator needs to enable the `BlockVolume` feature gate on the apiserver, controller-manager and the kubelet.

Prior to v1.9, the default behavior for all volume plugins was to create a filesystem on the persistent volume. With v1.9, the user can specify a `volumeMode` which will now support raw block devices in addition to file systems. Valid values for `volumeMode` are "Filesystem" or "Block". If left unspecified, `volumeMode` defaults to "Filesystem" internally. This is an optional API parameter.

### Access Modes

Expand Down Expand Up @@ -499,7 +497,19 @@ spec:

## Raw Block Volume Support

Static provisioning support for Raw Block Volumes is included as an alpha feature for v1.9. With this change are some new API fields that need to be used to facilitate this functionality. Kubernetes v1.10 supports only Fibre Channel and Local Volume plugins for this feature.
{{< feature-state for_k8s_version="v1.9" state="alpha" >}}

To enable this feature in v1.9, the cluster administrator needs to enable the `BlockVolume` feature gate on the apiserver, controller-manager and the kubelet.

The following volume plugins support raw block volumes including dynamic provisioning where applicable:

* AWSElasticBlockStore
* AzureDisk
* FC (Fibre Channel)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only FC and iSCSI were implemented in 1.9? The rest were 1.10

* GCEPersistentDisk
* iSCSI
* Local volume
* RBD (Ceph Block Device)

### Persistent Volumes using a Raw Block Volume
```yaml
Expand Down