From c1601aab444e00fef7f0e3be478c7d8d93300070 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Mon, 22 Jan 2024 19:44:07 -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 b1375be..9299d99 100644 --- a/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md +++ b/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md @@ -85,7 +85,7 @@ helm upgrade -i longhorn longhorn/longhorn --namespace longhorn-system --create- !!! example "Be Patient - Come back in 20 Minutes" Rancher is going to take a while to fully set itself up, things will appear broken. Depending on how many resources you gave the cluster, it may take longer or shorter. A good ballpark is giving it at least 20 minutes to deploy itself before attempting to log into the webUI at https://awx.bunny-lab.io. - If you want to keep an eye on the deployment progress, you need to run the following command: `` + If you want to keep an eye on the deployment progress, you need to run the following command: `kubectl get pods --all-namespaces` The output should look like how it does below: ``` NAMESPACE NAME READY STATUS RESTARTS AGE