Update docs for installing Rancher on air gapped K3s cluster

This commit is contained in:
Catherine Luse
2020-03-30 13:33:04 -07:00
parent 75b3eef777
commit 844a73d6c5
12 changed files with 55 additions and 67 deletions
@@ -8,7 +8,7 @@ If you are experiencing issues while provisioning a cluster with enabled vSphere
- controller-manager (Manages volumes in vCenter)
- kubelet: (Mounts vSphere volumes to pods)
If your cluster is not configured with external [Cluster Logging]({{<baseurl>}}/rancher/v2.x/en/tools/logging/), you will need to SSH into nodes to get the logs of the `kube-controller-manager` (running on one of the control plane nodes) and the `kubelet` (pertaining to the node where the stateful pod has been scheduled).
If your cluster is not configured with external [Cluster Logging]({{<baseurl>}}/rancher/v2.x//en/cluster-admin/tools//logging/), you will need to SSH into nodes to get the logs of the `kube-controller-manager` (running on one of the control plane nodes) and the `kubelet` (pertaining to the node where the stateful pod has been scheduled).
The easiest way to create a SSH session with a node is the Rancher CLI tool.