bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible AWX Operator.md

Browse Source
This commit is contained in:
Nicole Rappe
2024-01-22 20:25:59 -07:00
parent 77942056f0
commit 33131f6a3b
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible AWX Operator.md
View File

@ -100,9 +100,6 @@ After you have deployed AWX into the cluster, it will not be immediately accessi
The RKE2 Cluster will translate `awx.bunny-lab.io` to the AWX web-service container(s) automatically. SSL certificates are not covered in this documentation, but suffice to say, the can be configured on another reverse proxy such as Traefik or via Cert-Manager / JetStack. The process of setting this up goes outside the scope of this document. The RKE2 Cluster will translate `awx.bunny-lab.io` to the AWX web-service container(s) automatically. SSL certificates are not covered in this documentation, but suffice to say, the can be configured on another reverse proxy such as Traefik or via Cert-Manager / JetStack. The process of setting this up goes outside the scope of this document.
!!! 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.
!!! success "Accessing the AWX WebUI" !!! 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. If you have gotten this far, you should now be able to access AWX via the WebUI and log in.
@ -111,12 +108,15 @@ The RKE2 Cluster will translate `awx.bunny-lab.io` to the AWX web-service contai
AWX will generate its own secure password the first time you set up AWX. You can run the following command to retrieve it. AWX will generate its own secure password the first time you set up AWX. You can run the following command to retrieve it.
``` ```
kubectl get secret awx-admin-password -o jsonpath="{.data.password}" | base64 --decode ; echo kubectl get secret awx-admin-password -n awx -o jsonpath="{.data.password}" | base64 --decode ; echo
``` ```
## Troubleshooting ## Troubleshooting
You may wish to want to track the deployment process to verify that it is actually doing something. There are a few Kubernetes commands that can assist with this listed below. You may wish to want to track the deployment process to verify that it is actually doing something. There are a few Kubernetes commands that can assist with this listed below.
!!! 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 ### Show the container deployment progress for AWX
``` ```
kubectl get pods -n awx kubectl get pods -n awx