Files
kubernetes/pkg/volume
Kubernetes Submit Queue 3fcb7cb377 Merge pull request #42170 from rootfs/azure-file-prv
Automatic merge from submit-queue (batch tested with PRs 43642, 43170, 41813, 42170, 41581)

Enable storage class support in Azure File volume

**What this PR does / why we need it**:
Support StorageClass in Azure file volume

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

**Special notes for your reviewer**:

**Release note**:

```release-note
Support StorageClass in Azure file volume

```
2017-03-24 19:04:28 -07:00
..
2017-03-02 14:59:59 -05:00
2017-03-02 14:59:59 -05:00
2017-03-02 14:59:59 -05:00
2017-03-02 14:59:59 -05:00
2017-03-02 14:59:59 -05:00
2017-03-02 14:59:59 -05:00
2017-03-02 14:59:59 -05:00
2017-03-02 14:59:59 -05:00
2017-03-02 14:59:59 -05:00
2017-03-02 14:59:59 -05:00
2017-03-02 14:59:59 -05:00
2017-03-02 14:59:59 -05:00
2017-03-09 18:24:37 -05:00
2016-07-16 13:48:21 -04:00
2017-03-02 15:01:59 -08:00
2017-03-02 15:01:59 -08:00
2017-03-02 15:01:59 -08:00
2017-03-02 15:01:59 -08:00
2017-02-27 09:12:15 -05:00
2017-03-02 14:59:59 -05:00

Multipath

To leverage multiple paths for block storage, it is important to perform the multipath configuration on the host. If your distribution does not provide /etc/multipath.conf, then you can either use the following minimalistic one:

defaults {
    find_multipaths yes
    user_friendly_names yes
}

or create a new one by running:

$ mpathconf --enable

Finally you'll need to ensure to start or reload and enable multipath:

$ systemctl enable multipathd.service
$ systemctl restart multipathd.service

Note: Any change to multipath.conf or enabling multipath can lead to inaccessible block devices, because they'll be claimed by multipath and exposed as a device in /dev/mapper/*.

Some additional informations about multipath can be found in the iSCSI documentation