diff --git a/docs/book/cluster_architecture.md b/docs/book/cluster_architecture.md index 66256fac0..9adb9e616 100644 --- 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 deleted file mode 100755 index 7a6c0e01d..000000000 Binary files a/docs/book/images/clusterbased.png and /dev/null differ diff --git a/docs/book/images/datacenterbased.png b/docs/book/images/datacenterbased.png deleted file mode 100755 index bd1d49f88..000000000 Binary files a/docs/book/images/datacenterbased.png and /dev/null differ diff --git a/docs/book/images/in-tree-arch.png b/docs/book/images/in-tree-arch.png deleted file mode 100644 index 2471e2775..000000000 Binary files a/docs/book/images/in-tree-arch.png and /dev/null differ diff --git a/docs/book/images/out-of-tree-arch.png b/docs/book/images/out-of-tree-arch.png deleted file mode 100644 index 1ea9ef0f0..000000000 Binary files a/docs/book/images/out-of-tree-arch.png and /dev/null differ diff --git a/docs/book/images/pitfalls.png b/docs/book/images/pitfalls.png deleted file mode 100755 index 957659080..000000000 Binary files a/docs/book/images/pitfalls.png and /dev/null differ diff --git a/docs/book/images/vCenter.png b/docs/book/images/vCenter.png deleted file mode 100644 index 0b6f5ba1c..000000000 Binary files a/docs/book/images/vCenter.png and /dev/null differ diff --git a/docs/book/images/vsphere-in-tree-architecture.png b/docs/book/images/vsphere-in-tree-architecture.png deleted file mode 100644 index e7bbe9863..000000000 Binary files a/docs/book/images/vsphere-in-tree-architecture.png and /dev/null differ diff --git a/docs/book/images/vsphere-out-of-tree-architecture.png b/docs/book/images/vsphere-out-of-tree-architecture.png deleted file mode 100644 index 9587f4f66..000000000 Binary files a/docs/book/images/vsphere-out-of-tree-architecture.png and /dev/null differ diff --git a/docs/book/images/whichdatastore.png b/docs/book/images/whichdatastore.png deleted file mode 100755 index 6d43a9914..000000000 Binary files a/docs/book/images/whichdatastore.png and /dev/null differ diff --git a/docs/book/kubernetes_concepts.md b/docs/book/kubernetes_concepts.md index a6bbdb517..de8fa6f85 100644 --- a/docs/book/kubernetes_concepts.md +++ b/docs/book/kubernetes_concepts.md @@ -17,7 +17,7 @@ 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 @@ -25,7 +25,7 @@ Out-of-tree cloud provider refers to integrations that can be developed, built a 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