Update Containers/Kubernetes/Rancher RKE2/AWX Operator/Ansible Operator.md
This commit is contained in:
@ -97,24 +97,23 @@ The RKE2 Cluster will translate `awx.bunny-lab.io` to the AWX web-service contai
|
|||||||
- AWX WebUI: https://awx.bunny-lab.io
|
- 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. You can run the following command to retrieve it.
|
||||||
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.
|
```
|
||||||
- Rancher WebUI: https://awx-cluster.cyberstrawberry.net
|
kubectl get secret awx-admin-password -o jsonpath="{.data.password}" | base64 --decode ; echo
|
||||||
- Alternatively, you can try running the following command to pull the admin password / secret automatically
|
```
|
||||||
```
|
|
||||||
kubectl get secret awx-admin-password -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.
|
||||||
|
|
||||||
### Show the container deployment progress for AWX
|
### Show the container deployment progress for AWX
|
||||||
```
|
```
|
||||||
kubectl get pods -n awx
|
kubectl get pods -n awx
|
||||||
```
|
```
|
||||||
|
|
||||||
### AWX-Manager Deployment Logs
|
### 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.
|
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.
|
||||||
```
|
```
|
||||||
kubectl logs -n awx awx-operator-controller-manager-6c58d59d97-qj2n2 -c awx-manager
|
kubectl logs -n awx awx-operator-controller-manager-6c58d59d97-qj2n2 -c awx-manager
|
||||||
```
|
```
|
||||||
:::note
|
!!! note
|
||||||
The `-6c58d59d97-qj2n2` noted at the end of the Kubernetes "Pod" mentioned in the command above is randomized. You will need to change it based on the name shown when running the `kubectl get pods -n awx` command.
|
The `-6c58d59d97-qj2n2` noted at the end of the Kubernetes "Pod" mentioned in the command above is randomized. You will need to change it based on the name shown when running the `kubectl get pods -n awx` command.
|
||||||
:::
|
|
Reference in New Issue
Block a user