From 44811113af17beaed52358320b78916212725bf4 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Mon, 22 Jan 2024 20:31:04 -0700 Subject: [PATCH] Update Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible AWX Operator.md --- .../Rancher RKE2/AWX Operator/Ansible AWX Operator.md | 5 ----- 1 file changed, 5 deletions(-) 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 ac0cf33..38d1f7c 100644 --- a/Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible AWX Operator.md +++ b/Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible AWX Operator.md @@ -127,11 +127,6 @@ You may wish to want to track the deployment process to verify that it is actual !!! failure "Nested Reverse Proxy Issues" My homelab environment primarily uses a Traefik reverse proxy to handle all communications, but AWX currently has issues running behind Traefik/NGINX, and documentation outlining how to fix this does not exist here yet. For the time being, when you create the DNS record, use an `A` record pointing directly to the IP address of the Virtual Machine running the Rancher / AWX Operator cluster. -### Show the container deployment progress for AWX -``` -kubectl get pods -n awx -``` - ### AWX-Manager Deployment Logs You may want to track the internal logs of the `awx-manager` container which is responsible for the majority of the automated deployment of AWX. You can do so by running the command below. ```