Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.2", GitCommit:"477efc3cbe6a7effca06bd1452fa356e2201e1ee", GitTreeState:"clean", BuildDate:"2017-04-19T20:33:11Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.3", GitCommit:"0480917b552be33e2dba47386e51decb1a211df6", GitTreeState:"clean", BuildDate:"2017-05-10T15:38:08Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}

Environment:
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1381.1.0
VERSION_ID=1381.1.0
BUILD_ID=2017-04-25-2232
PRETTY_NAME="Container Linux by CoreOS 1381.1.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

• Linux server37 4.10.12-coreos Unit test coverage in Kubelet is lousy. (~30%) #1 SMP Tue Apr 25 22:08:35 UTC 2017 x86_64 Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz GenuineIntel GNU/Linux

• hyperkube

Access modes for PVC resources does not work as expected, for example if using dynamic provision with ROX mode, for glusterFS provisioner it allows perform write operation on volume moreover it can be used as RWX.

I expect when using accessModes it should work properly, at least if i creating RO volume it should be mounted as RO

Create PVC with AccessMode param as ReadOnlyMany, then assign it to POD and try to write something, for example touch <path/to/mount>/test, you should be able to write file in "ReadOnly" filesystem