Merge pull request #196 from andrewsykim/vsphere-docs

docs: use full raw github content URLs for images
kubernetes · Jun 11, 2019 · 9224d17 · 9224d17
2 parents a3cb570 + 0f6f2f1
commit 9224d17
Show file tree

Hide file tree

Showing 11 changed files with 4 additions and 4 deletions.
diff --git a/docs/book/cluster_architecture.md b/docs/book/cluster_architecture.md
@@ -9,7 +9,7 @@ file and credentials. What the config file should look like and how the credenti
 [Installing and Operating the vSphere Cloud Provider](#installing-operating-the-vsphere-cloud-provider). For now, assume that
 every component has access to a config file and credentials which allow access to vCenter.
 
-![vSphere In-Tree Cloud Provider Architecture](/images/vsphere-in-tree-architecture.png "vSphere In-Tree Cloud Provider Architecture")
+![vSphere In-Tree Cloud Provider Architecture](https://github.com/kubernetes/cloud-provider-vsphere/raw/master/docs/images/vsphere-in-tree-architecture.png "vSphere In-Tree Cloud Provider Architecture")
 
 **Note**: this diagram only illustrates which components in your cluster should be connecting to vCenter.
 
@@ -21,6 +21,6 @@ the cloud-controller-manager. Therefore, only the cloud-controller-manager is re
 in order to connnect to vCenter. Similar to the in-tree case, how to configure these will be covered in [Installing and Operating the vSphere Cloud Provider](#installing-operating-the-vsphere-cloud-provider). For now, assume that the cloud-controller-manager has access
 to a confile file and credentials which allow access to vCenter.
 
-![vSphere Out-of-Tree Cloud Provider Architecture](/images/vsphere-out-of-tree-architecture.png "vSphere Out-of-Tree Cloud Provider Architecture")
+![vSphere Out-of-Tree Cloud Provider Architecture](https://github.com/kubernetes/cloud-provider-vsphere/raw/master/docs/images/vsphere-out-of-tree-architecture.png "vSphere Out-of-Tree Cloud Provider Architecture")
 
 **Note**: this diagram only illustrates which components in your cluster should be connecting to vCenter.
diff --git a/docs/book/images/clusterbased.png b/docs/book/images/clusterbased.png
diff --git a/docs/book/images/datacenterbased.png b/docs/book/images/datacenterbased.png
diff --git a/docs/book/images/in-tree-arch.png b/docs/book/images/in-tree-arch.png
diff --git a/docs/book/images/out-of-tree-arch.png b/docs/book/images/out-of-tree-arch.png
diff --git a/docs/book/images/pitfalls.png b/docs/book/images/pitfalls.png
diff --git a/docs/book/images/vCenter.png b/docs/book/images/vCenter.png
diff --git a/docs/book/images/vsphere-in-tree-architecture.png b/docs/book/images/vsphere-in-tree-architecture.png
diff --git a/docs/book/images/vsphere-out-of-tree-architecture.png b/docs/book/images/vsphere-out-of-tree-architecture.png
diff --git a/docs/book/images/whichdatastore.png b/docs/book/images/whichdatastore.png
diff --git a/docs/book/kubernetes_concepts.md b/docs/book/kubernetes_concepts.md
@@ -17,15 +17,15 @@ As of writing this, there are two modes of cloud provider integrations: in-tree
 In-tree cloud providers refers to cloud provider integrations that are directly compiled and built into the core Kubernetes components.
 This also means that the integration is also developed within the same source code repository as Kubernetes core. As a result, updates to the cloud
 
-![In-Tree Cloud Provider Architecture](/images/in-tree-arch.png "Kubernetes In-Tree Cloud Provider Architecture - from k8s.io/website")
+![In-Tree Cloud Provider Architecture](https://github.com/kubernetes/cloud-provider-vsphere/raw/master/docs/images/in-tree-arch.png "Kubernetes In-Tree Cloud Provider Architecture - from k8s.io/website")
 
 ### Out-of-Tree Cloud Providers
 
 Out-of-tree cloud provider refers to integrations that can be developed, built and released independent of Kubernetes core. This requires
 adding a new component to the cluster called the cloud-controller-manager. The cloud-controller-manager is responsible for running all the
 cloud-specific control loops that were previously run in core components like the kube-controller-manager and the kubelet.
 
-![Out-of-Tree Cloud Provider Architecture](/images/out-of-tree-arch.png "Kubernetes Out-of-Tree Cloud Provider Architecture - from k8s.io/website")
+![Out-of-Tree Cloud Provider Architecture](https://github.com/kubernetes/cloud-provider-vsphere/raw/master/docs/images/out-of-tree-arch.png "Kubernetes Out-of-Tree Cloud Provider Architecture - from k8s.io/website")
 
 ### In-Tree vs Out-of-Tree