Update Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible Operator.md
This commit is contained in:
@ -4,7 +4,6 @@ Deploying a Rancher RKE2 Cluster-based Ansible AWX Operator server. This can sc
|
||||
!!! note Prerequisites
|
||||
This document assumes you are running **Ubuntu Server 20.04** or later with at least 8GB of memory, 4 CPU cores, and 64GB of storage.
|
||||
|
||||

|
||||
## Deploy Rancher RKE2 Cluster
|
||||
You will need to deploy a [Rancher RKE2 Cluster](https://docs.bunny-lab.io/Containers/Kubernetes/Rancher%20RKE2/Rancher%20RKE2%20Cluster/) on an Ubuntu Server-based virtual machine. After this phase, you can focus on the Ansible AWX-specific deployment. A single ControlPlane node is all you need to set up AWX, additional infrastructure can be added after-the-fact.
|
||||
|
||||
@ -92,7 +91,11 @@ The RKE2 Cluster will translate `awx.bunny-lab.io` to the AWX web-service contai
|
||||
!!! 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.
|
||||
|
||||
- AWX WebUI: https://awx.bunny-lab.io
|
||||
!!! success "Accessing the AWX WebUI"
|
||||
If you have gotten this far, you should now be able to access AWX via the WebUI and log in.
|
||||
|
||||
- AWX WebUI: https://awx.bunny-lab.io
|
||||

|
||||
|
||||
### Retrieving the Auto-Generated Admin Password
|
||||
AWX will generate its own secure password the first time you set up AWX. This password is stored as a *secret* in Kubernetes. You can navigate to the WebUI of Rancher in the RKE2 Cluster as long as you have a DNS record matching the hostname you assigned to Rancher the first time you signed in.
|
||||
|
Reference in New Issue
Block a user