From 42d7f845c8c388c505ecacf8fa9040e1625a2738 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Thu, 8 Feb 2024 00:24:01 -0700 Subject: [PATCH] Update Docker & Kubernetes/Servers/Kubernetes Clusters/Rancher RKE2.md --- Docker & Kubernetes/Servers/Kubernetes Clusters/Rancher RKE2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Docker & Kubernetes/Servers/Kubernetes Clusters/Rancher RKE2.md b/Docker & Kubernetes/Servers/Kubernetes Clusters/Rancher RKE2.md index 67db709..6196ce9 100644 --- a/Docker & Kubernetes/Servers/Kubernetes Clusters/Rancher RKE2.md +++ b/Docker & Kubernetes/Servers/Kubernetes Clusters/Rancher RKE2.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: `kubectl get pods --all-namespaces` + If you want to keep an eye on the deployment progress, you need to run the following command: `KUBECONFIG=/etc/rancher/rke2/rke2.yaml kubectl get pods --all-namespaces` The output should look like how it does below: ``` NAMESPACE NAME READY STATUS RESTARTS AGE