Create shared-files folder and update links

Add missing image

versioned_docs/version-2.0-2.4/getting-started/installation-and-upgrade/installation-requirements/port-requirements.md

@@ -210,7 +210,7 @@ The following table depicts the port requirements for [imported clusters](../../
 
 These ports are typically opened on your Kubernetes nodes, regardless of what type of cluster it is.
 
-import CommonPortsTable from 'shared-files/_common-ports-table.md';
+import CommonPortsTable from '../../../shared-files/_common-ports-table.md';
 
 <CommonPortsTable />
 

versioned_docs/version-2.0-2.4/getting-started/introduction/overview.md

@@ -60,6 +60,6 @@ After a cluster is created with Rancher, a cluster administrator can manage clus
 
 The following table summarizes the options and settings available for each cluster type:
 
-import ClusterCapabilitiesTable from 'shared-files/_cluster-capabilities-table.md';
+import ClusterCapabilitiesTable from '../../shared-files/_cluster-capabilities-table.md';
 
 <ClusterCapabilitiesTable />

versioned_docs/version-2.0-2.4/pages-for-subheaders/cluster-configuration.md

@@ -18,7 +18,7 @@ The options and settings available for an existing cluster change based on the m
 
 The following table summarizes the options and settings available for each cluster type:
 
-import ClusterCapabilitiesTable from 'shared-files/_cluster-capabilities-table.md';
+import ClusterCapabilitiesTable from '../shared-files/_cluster-capabilities-table.md';
 
 <ClusterCapabilitiesTable />
 

versioned_docs/version-2.0-2.4/pages-for-subheaders/kubernetes-clusters-in-rancher-setup.md

@@ -28,7 +28,7 @@ This section covers the following topics:
 
 The following table summarizes the options and settings available for each cluster type:
 
-import ClusterCapabilitiesTable from 'shared-files/_cluster-capabilities-table.md';
+import ClusterCapabilitiesTable from '../shared-files/_cluster-capabilities-table.md';
 
 <ClusterCapabilitiesTable />
 

versioned_docs/version-2.0-2.4/pages-for-subheaders/manage-clusters.md

@@ -23,7 +23,7 @@ Alternatively, you can switch between projects and clusters directly in the navi
 
 After clusters have been [provisioned into Rancher](kubernetes-clusters-in-rancher-setup.md), [cluster owners](../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac/cluster-and-project-roles.md#cluster-roles) will need to manage these clusters. There are many different options of how to manage your cluster.
 
-import ClusterCapabilitiesTable from 'shared-files/_cluster-capabilities-table.md';
+import ClusterCapabilitiesTable from '../shared-files/_cluster-capabilities-table.md';
 
 <ClusterCapabilitiesTable />
 

versioned_docs/version-2.0-2.4/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/vsphere/prior-to-v2.0.4.md

@@ -26,7 +26,7 @@ In the **Account Access** section, enter the vCenter FQDN or IP address and the
 
 # Scheduling
 
-Choose what hypervisor the virtual machine will be scheduled to. 
+Choose what hypervisor the virtual machine will be scheduled to.
 
 | Parameter                | Required | Description |
 |:------------------------|:--------:|:------------------------------------------------------------|
@@ -65,7 +65,7 @@ To enable disk UUIDs for all VMs created for a cluster,
 3. Under **Instance Options** click on **Add Parameter**.
 4. Enter `disk.enableUUID` as key with a value of **TRUE**.
 
-    ![](/img/rke/vsphere-nodedriver-enable-uuid.png)
+    ![](/img/vsphere-nodedriver-enable-uuid.png)
 
 5. Click **Create** or **Save**.
 
@@ -81,7 +81,7 @@ Optionally, you can:
 - Assign labels to the VMs that can be used as a base for scheduling rules in the cluster.
 - Customize the configuration of the Docker daemon on the VMs that will be created.
 
-> **Note:** Custom attributes are a legacy feature that will eventually be removed from vSphere. 
+> **Note:** Custom attributes are a legacy feature that will eventually be removed from vSphere.
 
 # Cloud Init