From aab6b9aa9f221ce016f7df53198afa16739a0e36 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Mon, 22 Jan 2024 19:46:11 -0700 Subject: [PATCH] Update Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md --- Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md b/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md index 9299d99..35918d6 100644 --- a/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md +++ b/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md @@ -150,6 +150,12 @@ helm upgrade -i longhorn longhorn/longhorn --namespace longhorn-system --create- ### Log into webUI At this point, you can log into the webUI at https://awx.bunny-lab.io using the default `bootStrapAllTheThings` password, or whatever password you configured, it will prompt you to change the password after logging in either way. From here, you can deploy more nodes, or deploy single-node workloads such as an [Ansible AWX Operator](https://docs.bunny-lab.io/Containers/Kubernetes/Rancher%20RKE2/AWX%20Operator/Ansible%20AWX%20Operator/). +### Rebooting the ControlNode +If you ever find yourself needing to reboot the ControlNode, and need to run kubectl CLI commands, you will need to run the command below to import the cluster credentials upon every reboot: +``` +export KUBECONFIG=/etc/rancher/rke2/rke2.yaml +``` + ## Create Additional ControlPlane Node(s) This is the part where you can add additional controlplane nodes to add additional redundancy to the RKE2 Cluster. This is important for high-availability environments.