From a57bc14618ea81e675e86bc97ca7592436bddd00 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Mon, 22 Jan 2024 19:48:19 -0700 Subject: [PATCH] Update Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md --- Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md b/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md index 35918d6..f0b6342 100644 --- a/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md +++ b/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md @@ -151,7 +151,7 @@ helm upgrade -i longhorn longhorn/longhorn --namespace longhorn-system --create- 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: +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. Reboots should take much less time to get the cluster ready again as compared to the original deployments. ``` export KUBECONFIG=/etc/rancher/rke2/rke2.yaml ```