From 39042f227a36c229104379004e128f942839b504 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Mon, 22 Jan 2024 20:19:56 -0700 Subject: [PATCH] Update Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible AWX Operator.md --- .../Rancher RKE2/AWX Operator/Ansible AWX Operator.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible AWX Operator.md b/Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible AWX Operator.md index 6020ca2..ff75da1 100644 --- a/Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible AWX Operator.md +++ b/Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible AWX Operator.md @@ -72,6 +72,13 @@ You will need to create these files all in the same directory using the content namespace: awx ``` +## Ensure the Kubernetes Cluster is Ready +Check that the status of the cluster is ready by running the following commands, it should appear similar to the [Rancher RKE2 Example](https://docs.bunny-lab.io/Containers/Kubernetes/Rancher%20RKE2/Rancher%20RKE2%20Cluster/#install-helm-rancher-certmanager-jetstack-rancher-and-longhorn): +``` +export KUBECONFIG=/etc/rancher/rke2/rke2.yaml +kubectl get pods --all-namespaces +``` + ## Deploy AWX using Kustomize Now it is time to tell Kubernetes to read the configuration files using Kustomize (*built-in to newer versions of Kubernetes*) to deploy AWX into the cluster. !!! warning "Be Patient"