tell user how to check if a default storage class is defined

kubeflow · Dec 18, 2018 · 1ba9275 · 1ba9275
1 parent 90ecfae
commit 1ba9275
Showing 1 changed file with 11 additions and 2 deletions.
diff --git a/object_detection/setup.md b/object_detection/setup.md
@@ -66,7 +66,16 @@ does not support this feature you can modify the `accessMode` value to create th
 and before you execute the tf-job to train the model add a `nodeSelector:` configuration to execute the pods
 in the same node. You can find more about assigning pods to specific nodes [here](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/)
 
-This step assumes that your K8s cluster has [Dynamic Volume Provisioning](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/) enabled.
+This step assumes that your K8s cluster has [Dynamic Volume Provisioning](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/) enabled and
+the default Storage Class is created. You can check if the assumption is ready like below (a storageclass with `(defaut)` notation need exist):
+
+```
+$ kubectl get storageclass
+NAME                 PROVISIONER               AGE
+standard (default)   kubernetes.io/gce-pd      1d
+gold                 kubernetes.io/gce-pd      1d
+```
+
 Otherwise you can find that the PVC remains `Pending` status.
 
 ```
@@ -75,7 +84,7 @@ NAME        STATUS    VOLUME    CAPACITY   ACCESS MODES   STORAGECLASS   AGE
 pets-pvc    Pending                                                      28s
 ```
 
-You can create a PV with your NFS server to make the PVC work.
+If your cluster doesn't have defined default storageclass, you can create a PV with your NFS server to make the PVC work.
 
 ```
 # Replace YOUR_NFS_SERVER_IP with your NFS server IP, saying 10.0.0.1; replace YOUR_NFS_SERVER_EXPORT_DIR with your NFS server mountable directory, saying /tmp.