I just wanted to follow up on ZhangFan4's question.  He reports that he was able to work around his issues. The user reports that he does have CentOS 7.4.   His paths for the feature gates and Docker service were different than that in the docs.  He was able to find the files in different locations and modify them appropriately.   He did modify the verify.kubernetes script MINION_PROCS  to point to his location.  He also installed the VxFlex OS Storage Data Client (SDC) on the Master. I also had issues with setting up the feature gates.  I found that copy and paste from the Prod Guide did not work as expected.  To help I ran the yaml through a yaml checker to assist with spacing, alignment, and dashes. I also ran Flo_csl's recommended command to check the feature gates.  Mine now show enabled:  systemctl status kubelet.service -l â kubelet.service - kubelet: The Kubernetes Node Agent Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled)Drop-In: /usr/lib/systemd/system/kubelet.service.dââ10-kubeadm.confActive: active (running) since Thu 2019-06-27 16:48:23 EDT; 4 days agoDocs: [URL] PID: 7838 (kubelet)Tasks: 30Memory: 143.9MCGroup: /system.slice/kubelet.serviceââ7838 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --allow-privileged=true --feature-gates=VolumeSnapshotDataSource=true,KubeletPluginsWatcher=true,CSINodeInfo=true,CSIDriverRegistry=true,BlockVolume=true,CSIBlockVolume=true--config=/var/lib/kubelet/config.yaml --cgroup-driver=systemd --network-plugin=cni --pod-infra-container-image=k8s.gcr.io/pause:3.1
Customer Env:  K8S 1.13.3 K8S host CentOS Linux 7.4 VxFlex 3.0.769 *********************************************** 3SDS/MDM：Data1:192.168.1.2-4Data2:192.168.2.2-4App：10.8.192.89-91 Gateway 10.8.192.89Primary MDM 10.8.192.90 System ID MDPM IPs7a5ada7d5a833e0f 10.8.192.89 10.8.192.90 **************************************************K8S： kube-master 10.8.192.27 kube-m1 10.8.192.28 kube-m2 10.8.192.40 kube-m3  kube-worker 10.8.192.39/41/44 ************************************************** As follow the below video and product guide: [URL]#enable-csi-in-k8s-cluster    **************************************************************************************** [root[NAME]-m1 helm]# sh install.vxflexosKubernetes version v1.13.3Kubernetes master nodes: 10.8.192.27 10.8.192.28 10.8.192.40Kubernetes minion nodes: 10.8.192.41 10.8.192.39 10.8.192.44Verifying the SDC installation.Retrieved 1 mdm(s)MDM-ID 7a5ada7d5a833e0f SDC ID e71b7b7500000004 INSTALLATION ID 0f7a6e0e2eb88757 IPs [0]-10.8.192.89 [1]-10.8.192.90Retrieved 1 mdm(s)MDM-ID 7a5ada7d5a833e0f SDC ID e71ba28500000007 INSTALLATION ID 0f7a6e0e2eb88757 IPs [0]-10.8.192.89 [1]-10.8.192.90Retrieved 1 mdm(s)MDM-ID 7a5ada7d5a833e0f SDC ID e71ba28600000008 INSTALLATION ID 0f7a6e0e2eb88757 IPs [0]-10.8.192.89 [1]-10.8.192.90Verifying the feature gates.node 10.8.192.27 proc /usr/bin/kubelet gate VolumeSnapshotDataSource=true failednode 10.8.192.27 proc /usr/bin/kubelet gate KubeletPluginsWatcher=true failednode 10.8.192.27 proc /usr/bin/kubelet gate CSINodeInfo=true failednode 10.8.192.27 proc /usr/bin/kubelet gate CSIDriverRegistry=true failednode 10.8.192.27 proc /usr/bin/kubelet gate BlockVolume=true failednode 10.8.192.27 proc /usr/bin/kubelet gate CSIBlockVolume=true failednode 10.8.192.28 proc /usr/bin/kubelet gate VolumeSnapshotDataSource=true failednode 10.8.192.28 proc /usr/bin/kubelet gate KubeletPluginsWatcher=true failednode 10.8.192.28 proc /usr/bin/kubelet gate CSINodeInfo=true failednode 10.8.192.28 proc /usr/bin/kubelet gate CSIDriverRegistry=true failednode 10.8.192.28 proc /usr/bin/kubelet gate BlockVolume=true failednode 10.8.192.28 proc /usr/bin/kubelet gate CSIBlockVolume=true failednode 10.8.192.40 proc /usr/bin/kubelet gate VolumeSnapshotDataSource=true failednode 10.8.192.40 proc /usr/bin/kubelet gate KubeletPluginsWatcher=true failednode 10.8.192.40 proc /usr/bin/kubelet gate CSINodeInfo=true failednode 10.8.192.40 proc /usr/bin/kubelet gate CSIDriverRegistry=true failednode 10.8.192.40 proc /usr/bin/kubelet gate BlockVolume=true failednode 10.8.192.40 proc /usr/bin/kubelet gate CSIBlockVolume=true failednode 10.8.192.41 proc /usr/bin/kubelet gate VolumeSnapshotDataSource=true failednode 10.8.192.41 proc /usr/bin/kubelet gate KubeletPluginsWatcher=true failednode 10.8.192.41 proc /usr/bin/kubelet gate CSINodeInfo=true failednode 10.8.192.41 proc /usr/bin/kubelet gate CSIDriverRegistry=true failednode 10.8.192.41 proc /usr/bin/kubelet gate BlockVolume=true failednode 10.8.192.41 proc /usr/bin/kubelet gate CSIBlockVolume=true failednode 10.8.192.39 proc /usr/bin/kubelet gate VolumeSnapshotDataSource=true failednode 10.8.192.39 proc /usr/bin/kubelet gate KubeletPluginsWatcher=true failednode 10.8.192.39 proc /usr/bin/kubelet gate CSINodeInfo=true failednode 10.8.192.39 proc /usr/bin/kubelet gate CSIDriverRegistry=true failednode 10.8.192.39 proc /usr/bin/kubelet gate BlockVolume=true failednode 10.8.192.39 proc /usr/bin/kubelet gate CSIBlockVolume=true failednode 10.8.192.44 proc /usr/bin/kubelet gate VolumeSnapshotDataSource=true failednode 10.8.192.44 proc /usr/bin/kubelet gate KubeletPluginsWatcher=true failednode 10.8.192.44 proc /usr/bin/kubelet gate CSINodeInfo=true failednode 10.8.192.44 proc /usr/bin/kubelet gate CSIDriverRegistry=true failednode 10.8.192.44 proc /usr/bin/kubelet gate BlockVolume=true failednode 10.8.192.44 proc /usr/bin/kubelet gate CSIBlockVolume=true failedfail: 1*******************************************************************************Warning: Kubernetes --feature-gates not correctly configured... it may not work*******************************************************************************NAME: vxflexosLAST DEPLOYED: Wed Jun 5 13:48:46 2019NAMESPACE: vxflexosSTATUS: DEPLOYED RESOURCES:==> v1/Pod(related)NAME READY STATUS RESTARTS AGEvxflexos-node-55crv 0/2 ContainerCreating 0 0svxflexos-node-5dfg6 0/2 ContainerCreating 0 0svxflexos-node-qpfzj 0/2 ContainerCreating 0 0svxflexos-controller-0 0/4 ContainerCreating 0 0s ==> v1/StorageClassNAME PROVISIONER AGEvxflexos-xfs csi-vxflexos 1svxflexos (default) csi-vxflexos 1s ==> v1/ServiceAccountNAME SECRETS AGEvxflexos-controller 1 1svxflexos-node 1 1s ==> v1/ClusterRoleNAME AGEvxflexos-controller 1svxflexos-node 1s ==> v1/ClusterRoleBindingNAME AGEvxflexos-controller 0svxflexos-node 0s ==> v1beta2/DaemonSetNAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGEvxflexos-node 3 3 0 3 0 0s  ==> v1beta1/StatefulSetNAME DESIRED CURRENT AGEvxflexos-controller 1 1 0s ==> v1alpha1/CSIDriverNAME AGEvxflexos 0s NAME READY STATUS RESTARTS AGEvxflexos-controller-0 0/4 ErrImagePull 0 10svxflexos-node-55crv 0/2 ErrImagePull 0 10svxflexos-node-5dfg6 0/2 ImagePullBackOff 0 10svxflexos-node-qpfzj 0/2 ErrImagePull 0 10sNAME READY STATUS RESTARTS AGEvxflexos-controller-0 0/4 ErrImagePull 0 15svxflexos-node-55crv 0/2 ErrImagePull 0 15svxflexos-node-5dfg6 0/2 ImagePullBackOff 0 15svxflexos-node-qpfzj 0/2 ErrImagePull 0 15sNAME READY STATUS RESTARTS AGEvxflexos-controller-0 0/4 ImagePullBackOff 0 20svxflexos-node-55crv 0/2 ImagePullBackOff 0 20svxflexos-node-5dfg6 0/2 ImagePullBackOff 0 20svxflexos-node-qpfzj 0/2 ImagePullBackOff 0 20sCSIDrivers:NAME AGEvxflexos 20sCSINodeInfos:NAME AGEkube-n1 1dkube-n2 1dkube-n3 1dStorageClasses:NAME PROVISIONER AGEvxflexos (default) csi-vxflexos 22svxflexos-xfs csi-vxflexos 22sNo resources found.installing volumesnapshotclassvolumesnapshotclass.snapshot.storage.k8s.io/vxflexos-snapclass createdVolumeSnapshotClasses:NAME AGEvxflexos-snapclass 1s  
CSI 1.0 deployment failed on k8s 1.13.3