Apply Divio and update links

versioned_docs/version-2.0-2.4/troubleshooting/kubernetes-components/kubernetes-components.md

@@ -1,18 +0,0 @@
----
-title: Kubernetes Components
-weight: 100
----
-
-The commands and steps listed in this section apply to the core Kubernetes components on [Rancher Launched Kubernetes]({{<baseurl>}}/rancher/v2.0-v2.4/en/cluster-provisioning/rke-clusters/) clusters.
-
-This section includes troubleshooting tips in the following categories:
-
-- [Troubleshooting etcd Nodes]({{<baseurl>}}/rancher/v2.0-v2.4/en/troubleshooting/kubernetes-components/etcd)
-- [Troubleshooting Controlplane Nodes]({{<baseurl>}}/rancher/v2.0-v2.4/en/troubleshooting/kubernetes-components/controlplane)
-- [Troubleshooting nginx-proxy Nodes]({{<baseurl>}}/rancher/v2.0-v2.4/en/troubleshooting/kubernetes-components/nginx-proxy)
-- [Troubleshooting Worker Nodes and Generic Components]({{<baseurl>}}/rancher/v2.0-v2.4/en/troubleshooting/kubernetes-components/worker-and-generic)
-
-# Kubernetes Component Diagram
-
-![Cluster diagram]({{<baseurl>}}/img/rancher/clusterdiagram.svg)<br/>
-<sup>Lines show the traffic flow between components. Colors are used purely for visual aid</sup>

versioned_docs/version-2.0-2.4/troubleshooting/kubernetes-components/troubleshooting-controlplane-nodes.md

@@ -29,7 +29,7 @@ bdf3898b8063        rancher/hyperkube:v1.11.5-rancher1   "/opt/rke-tools/en..."
 
 # Controlplane Container Logging
 
-> **Note:** If you added multiple nodes with the `controlplane` role, both `kube-controller-manager` and `kube-scheduler` use a leader election process to determine the leader. Only the current leader will log the performed actions. See [Kubernetes leader election]({{<baseurl>}}/rancher/v2.0-v2.4/en/troubleshooting/kubernetes-resources/#kubernetes-leader-election) how to retrieve the current leader.
+> **Note:** If you added multiple nodes with the `controlplane` role, both `kube-controller-manager` and `kube-scheduler` use a leader election process to determine the leader. Only the current leader will log the performed actions. See [Kubernetes leader election](../other-troubleshooting-tips/kubernetes-resources.md#kubernetes-leader-election) how to retrieve the current leader.
 
 The logging of the containers can contain information on what the problem could be.