# Completing the AWX Operator installation **URL:** \ **Category:** AWX Project\ **Tags:** awx\ **Created:** [July 20, 2023, 4:14pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250 "2023-07-20T16:14:41Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [July 20, 2023, 4:14pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/1 "2023-07-20T16:14:41Z")
Hi I’ve followed the excellent and detailed instructions for installing AWX Operator at [GitHub - ansible/awx-operator: An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖](https://github.com/ansible/awx-operator#basic-install). But the instructions don’t say what to do after the following command returns a URL: # minikube service -n awx awx-demo-service --url [http://192.168.49.2:31287](http://192.168.49.2:31287) I want to be able to access AWX by connecting to a URL on this system. Where are the instructions that explain how to do this? Looking at [GitHub - ansible/awx: AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.](https://github.com/ansible/awx), I see a link to the Red Hat Tower site. Is that the correct place for AWX getting started information? Thanks! tl ---
**Author:** ![Thomas\_Plank](https://avatars.discourse-cdn.com/v4/letter/t/977dab/32.png) [@Thomas\_Plank](https://forum.ansible.com/u/Thomas_Plank)\ **Post date:** [July 20, 2023, 6:59pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/2 "2023-07-20T18:59:27Z")
You need to configure your cluster to know where to route the traffic coming in via a hostname. The term you are looking for is “ **ingress** ”. Keep reading the documentation on, there is a link to a demo video just below where you stopped reading. 😉 ---
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [July 21, 2023, 2:29pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/3 "2023-07-21T14:29:58Z")
Hi Thanks very much for the reply. I didn’t realize that the demo video contained needed documentation - hm :). I watched the video and followed along, typing the commands on my system. But things stopped working when I tried to execute these commands, seen in the video: ldpdd042:/tmp # kubectl get pods -l “[app.kubernetes.io/managed-by=awx-operator](http://app.kubernetes.io/managed-by=awx-operator)” NAME READY STATUS RESTARTS AGE awx-demo-postgres-13-0 1/1 Running 0 23h awx-demo-task-59869fb77d-vmsw9 4/4 Running 0 23h awx-demo-web-86644d58d9-ks9xj 3/3 Running 0 23h ldpdd042:/tmp # kubectl get svc -l “[app.kubernetes.io/managed-by=awx-operator](http://app.kubernetes.io/managed-by=awx-operator)” NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE awx-demo-postgres-13 ClusterIP None 5432/TCP 23h awx-demo-service NodePort 10.102.50.41 80:31287/TCP 23h ldpdd042:/tmp # kubectl iexec awx-demo /bin/bash error: unknown command “iexec” for “kubectl” Did you mean this? exec ldpdd042:/tmp # kubectl exec awx-demo /bin/bash kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] – [COMMAND] instead. Error from server (NotFound): pods “awx-demo” not found ldpdd042:/tmp # awx-manage version -bash: awx-manage: command not found ldpdd042:/tmp # Perhaps the video uses commands that have been replaced in the latest AWX? Thanks for any thoughts. tl ---
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [July 21, 2023, 2:59pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/4 "2023-07-21T14:59:58Z")
I stepped around the video’s kukectl exec step, followed along in the video and was able to get the expected response from the curl command. I did not, as the video described, deploy a second AWX instance with a NGINX Ingress Controller, because the basic install already seemed to provide this: ldpdd042:/tmp # minikube service list > ---------------|-------------------------------------------------|--------------|---------------------------| > > | NAMESPACE | NAME | TARGET PORT | URL | > | --- | --- | --- | --- | > | awx | awx-demo-postgres-13 | No node port | | > | awx | awx-demo-service | http/80 | [http://192.168.49.2:31287](http://192.168.49.2:31287) | > | awx | awx-operator-controller-manager-metrics-service | No node port | | > | default | kubernetes | No node port | | > | ingress-nginx | ingress-nginx-controller | http/80 | [http://192.168.49.2:30906](http://192.168.49.2:30906) | > > > > https/443 | [http://192.168.49.2:32371](http://192.168.49.2:32371) | > > > ingress-nginx | ingress-nginx-controller-admission | No node port | | > > > kube-system | kube-dns | No node port | | > > > ---------------|-------------------------------------------------|--------------|---------------------------| > > > ldpdd042:/tmp # Though this looks good to me, the video’s ‘kubectl get ingresses’ command does not found any: ldpdd042:/tmp # kubectl get ingresses No resources found in awx namespace. ldpdd042:/tmp # Noticing that the ingress services are in not in the default namespace, I appended the --namespace qualifier, but still didn’t ldpdd042:/tmp # kubectl get ingresses --namespace ingress-nginx No resources found in ingress-nginx namespace. ldpdd042:/tmp # Thoughts? Thanks tl ---
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [July 26, 2023, 12:54pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/5 "2023-07-26T12:54:14Z")
Hi Any suggestion on how the instructions in the demo aren’t working in my environment? Thanks ---
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [July 31, 2023, 8:00pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/6 "2023-07-31T20:00:22Z")
Hi Any change to the installation instructions for AWX Operator 2.5.0? Thanks tl ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [August 2, 2023, 6:39pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/7 "2023-08-02T18:39:56Z")
are you having problems using operator 2.5? there is nothing special about 2.5 in terms of installation AWX Team ---
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [August 2, 2023, 9:08pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/8 "2023-08-02T21:08:15Z")
Not yet. For the previous AWX Operator release, I followed the instructions (including the demo) for installing/configuring AWX Operator, but never got it to work. So I think I’ll start fresh with AWX Operator 2.5. I just went to [https://github.com/ansible/awx-operator](https://github.com/ansible/awx-operator), clicked on ‘Basic Install’ as I did before, and now get a 404 File not found error. ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [August 4, 2023, 5:32pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/9 "2023-08-04T17:32:46Z")
we were changing around the links yesterday, should work now [https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md](https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md) ---
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [August 8, 2023, 7:08pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/10 "2023-08-08T19:08:16Z")
Hi Thanks for this information! I followed the steps in [https://github.com/ansible/awx-operator/blob/devel/docs/installation/creating-a-minikube-cluster-for-testing.md](https://github.com/ansible/awx-operator/blob/devel/docs/installation/creating-a-minikube-cluster-for-testing.md) and then in [https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md](https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md); all went well. I then moved on to the demo at [https://asciinema.org/a/416946](https://asciinema.org/a/416946). Everything went great until time 1:51 of the demo. The demo describes use of the command ‘kubectl iexec awx-demo /bin/bash’. This failed on my system: ldpdd042:/tmp # kubectl iexec awx-demo /bin/bash error: unknown command “iexec” for “kubectl” Did you mean this? exec ldpdd042:/tmp # So, I guessed that the latest version of the command was ‘kubectl exec awx-demo – /bin/bash’, but this didn’t execute successfully: ldpdd042:/tmp # kubectl exec awx-demo – /bin/bash Error from server (NotFound): pods “awx-demo” not found ldpdd042:/tmp # even though the pods to seem to be available: kubectl get pods -n awx NAME READY STATUS RESTARTS AGE awx-demo-postgres-13-0 1/1 Running 0 19m awx-demo-task-748f66bfc7-bsgtt 4/4 Running 0 18m awx-demo-web-56b6f8df8c-bxrpc 3/3 Running 0 17m awx-operator-controller-manager-66c5b94884-m8xzb 2/2 Running 0 23m ldpdd042:/tmp # Any thoughts about what could be wrong? I’m trying to get AWX running so I can connect to its GUI. Thanks! tl ---
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [August 11, 2023, 3:50pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/11 "2023-08-11T15:50:02Z")
Can anyone tell me how to install AWX? The demo (which is part of the documentation) is out of date, and I don’t know how to create a working AWX environment. Thanks! ---
**Author:** ![Gertz](https://avatars.discourse-cdn.com/v4/letter/g/f07891/32.png) [@Gertz](https://forum.ansible.com/u/Gertz)\ **Post date:** [August 11, 2023, 4:08pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/12 "2023-08-11T16:08:39Z")
there is importatn part what you miss in commands " -n awx " is definicion of namespace. try kubectl exec -n awx awx-demo – /bin/bash. If you want to use command without -n awx use command " kubectl config set-context --current --namespace=awx" which set current session namespace to awx. this guide is working for latest release: [https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md](https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md) Also there is information about namespace. best, Gertz Dne pátek 11. srpna 2023 v 17:50:03 UTC+2 uživatel [terry....@dell.com](mailto:terry....@dell.com) napsal: ---
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [September 5, 2023, 6:47pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/13 "2023-09-05T18:47:43Z")
Hi gertz Thanks for the reply! I see now that I need to always specify the namespace (via ‘-n awx’) in kubectl commands. I was confused by the fact that, in [https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md](https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md), some kubectl commands use the option and some don’t. Working through the demo, I tried your command, but found that it still didn’t work: ldpdd042:/tmp # kubectl exec -n awx awx-demo – /bin/bash Error from server (NotFound): pods “awx-demo” not found even though awx pods are running: ldpdd042:/tmp # kubectl get pods -n awx NAME READY STATUS RESTARTS AGE awx-demo-postgres-13-0 1/1 Running 0 35m awx-demo-task-6d7b6489d-zrcqx 4/4 Running 0 35m awx-demo-web-7b96744696-hl4sp 3/3 Running 0 33m awx-operator-controller-manager-65ddfcbf7d-j4nzf 2/2 Running 0 40m ldpdd042:/tmp # I used the suggested contents of awx-demo.yaml: cat awx-demo.yaml ---
**Author:** ![Wei-Yen\_Tan](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wei-yen_tan/32/4111_2.png) [@Wei-Yen\_Tan](https://forum.ansible.com/u/Wei-Yen_Tan)\ **Post date:** [September 5, 2023, 6:49pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/14 "2023-09-05T18:49:24Z")
You used awx-demo. Not awx-demo-task-6d7b6489d-zrcqx ---
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [September 5, 2023, 6:59pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/15 "2023-09-05T18:59:56Z")
Hi Wei-Yen Ah, that makes sense, thanks! It’s necessary to add that the ‘task’ pod needs to be used in the ‘kubectl exec’ command to the documentation/demo (please). But, I’m still not seeing the response shown in the demo (which is 2 years old, so maybe isn’t correct anymore)? ldpdd042:~ # kubectl exec -n awx awx-demo-task-6d7b6489d-zrcqx – /bin/bash ldpdd042:~ # awx-manage version -bash: awx-manage: command not found ldpdd042:~ # Thoughts? Thanks! tl Internal Use - Confidential ---
**Author:** ![Wei-Yen\_Tan](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wei-yen_tan/32/4111_2.png) [@Wei-Yen\_Tan](https://forum.ansible.com/u/Wei-Yen_Tan)\ **Post date:** [September 5, 2023, 7:02pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/16 "2023-09-05T19:02:13Z")
What is your goal. What are you trying to achieve? ---
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [September 5, 2023, 7:55pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/17 "2023-09-05T19:55:46Z")
I want to install AWX and use it to manage my team’s Ansible activities via its UI. Internal Use - Confidential ---
**Author:** ![Wei-Yen\_Tan](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wei-yen_tan/32/4111_2.png) [@Wei-Yen\_Tan](https://forum.ansible.com/u/Wei-Yen_Tan)\ **Post date:** [September 5, 2023, 7:56pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/18 "2023-09-05T19:56:47Z")
No I mean why are you executing into containers. There should be no need for that ---
**Author:** ![tlemons](https://avatars.discourse-cdn.com/v4/letter/t/edb3f5/32.png) [@tlemons](https://forum.ansible.com/u/tlemons)\ **Post date:** [September 5, 2023, 8:00pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/19 "2023-09-05T20:00:44Z")
Oh. I’m just trying to follow the instructions to get a working AWX environment. When I completed the instructions in [https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md](https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md), there was no mention of how to USE the AWX environment. So I kept going with the demo, hoping the demo would tell me how to get a working AWX environment. If there is any easier way to just get a working AWX environment, please tell me what it is. Thanks Internal Use - Confidential ---
**Author:** ![Wei-Yen\_Tan](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wei-yen_tan/32/4111_2.png) [@Wei-Yen\_Tan](https://forum.ansible.com/u/Wei-Yen_Tan)\ **Post date:** [September 5, 2023, 8:02pm UTC](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250/20 "2023-09-05T20:02:49Z")
Did you create a node port or ingress [Next page](https://forum.ansible.com/t/completing-the-awx-operator-installation/38250.md?page=2)