Fixes as per issue #202 on Kubernetes docs (#1596)

* Remove unnecessary folders and fix filenames

* Fix as per the comments by Divyen

kubernetes-docs/_config.yml

@@ -12,7 +12,7 @@ site_title: Kubernetes vSphere Cloud Provider
 company_name: VMWare
 # this appears in the footer
 
-github_editme_path: vmware/docker-volume-vsphere/edit/gh-pages/jekyll-docs
+github_editme_path: vmware/docker-volume-vsphere/edit/gh-pages/kubernetes-docs
 # if you're using Github, provide the basepath to the branch you've created for reviews, following the sample here. if not, leave this value blank.
 
 disqus_shortname: idrbwjekyll

kubernetes-docs/_data/sidebars/home_sidebar.yml

@@ -23,10 +23,10 @@ entries:
         output: web
         subfolderitems:
         - title: Volumes
-          url: /k8s-vols.html
+          url: /kubernetes-volumes.html
           output: web
         - title: Persistent Volumes & Persistent Volumes Claims
-          url: /pv-pvc.html
+          url: /persistent-vols-claims.html
           output: web
         - title: Dynamic Provisioning & Storage Class
           url: /storageclass.html
@@ -35,19 +35,19 @@ entries:
           url: /statefulsets.html
           output: web
     - title: Storage Policy Based Management for Dynamic Provisioning
-      url: /spbm.html
+      url: /policy-based-mgmt.html
       output: web
     - title: High Availability of Kubernetes Cluster
-      url: /ha.html
+      url: /high-availability.html
       output: web
   - title: Deployment
     output: web
     folderitems:
       - title: Prerequistes
-        url: /prereq.html
+        url: /prerequisites.html
         output: web
       - title: Kubernetes Anywhere
-        url: /k8sanywhere.html
+        url: /kubernetes-anywhere.html
         output: web
       - title: Configurations on existing Kubernetes Cluster
         url: /existing.html

kubernetes-docs/faqs.md

@@ -18,20 +18,20 @@ VIC is infrastructure platform to run containerized workloads alongside traditio
 Yes as long as laptop supports nested virtualization you can try it on your laptop.
 
 ## Which Kubernetes distribution is supported ?
-vSphere Cloud Provider is available in vanilla Kubernetes and all distributions using Kubernetes v1.5 and above should support it. Please refer this [section.](/prereq.html)  
+vSphere Cloud Provider is available in vanilla Kubernetes and all distributions using Kubernetes v1.5 and above should support it. Please refer this [section.](/docker-volume-vsphere/kubernetes/prereq.html)  
 
 ## Can we deploy multiple Kubernetes Cluster on one vCenter? 
-Yes. Please refer this [section.](/existing.html)  
+Yes. Please refer this [section.](/docker-volume-vsphere/kubernetes/existing.html)  
 
 
 ## Can Kubernetes Cluster access storage from another vCenter? 
-Yes. Please refer this [section.](/existing.html)
+Yes. Please refer this [section.](/docker-volume-vsphere/kubernetes/existing.html)
 
 ## Which Operating System are supported ? 
-We support Photon, Ubuntu, Core OS, please check this section for [details](/prereq.html)
+We support Photon, Ubuntu, Core OS, please check this section for [details](/docker-volume-vsphere/kubernetes/prereq.html)
 
 ## How Kubernetes volumes can be made resilient to failures on vSAN datastore?
-Please check the HA section for [details.](/ha.html)
+Please check the HA section for [details.](/docker-volume-vsphere/kubernetes/ha.html)
 
 ## Can I enable SDRS on VMs hosting kubernetes cluster?
 No.

kubernetes-docs/k8s-vols.md → kubernetes-docs/kubernetes-volumes.md

@@ -21,22 +21,22 @@ vmkfstools -c 2G /vmfs/volumes/datastore1/volumes/myDisk.vmdk
 #vsphere-volume-pod.yaml
 
   apiVersion: v1
-   kind: Pod
-   metadata:
-     name: test-vmdk
-   spec:
-     containers:
-     - image: gcr.io/google_containers/test-webserver
-       name: test-container
-       volumeMounts:
-       - mountPath: /test-vmdk
-         name: test-volume
-     volumes:
-     - name: test-volume
-       # This VMDK volume must already exist.
-       vsphereVolume:
-         volumePath: "[datastore1] volumes/myDisk"
-         fsType: ext4
+  kind: Pod
+  metadata:
+    name: test-vmdk
+  spec:
+    containers:
+    - image: gcr.io/google_containers/test-webserver
+      name: test-container
+      volumeMounts:
+      - mountPath: /test-vmdk
+        name: test-volume
+    volumes:
+    - name: test-volume
+      # This VMDK volume must already exist.
+      vsphereVolume:
+        volumePath: "[datastore1] volumes/myDisk"
+        fsType: ext4
 ```
 
 **Create the pod**