I’ve followed the excellent and detailed instructions for installing AWX Operator at https://github.com/ansible/awx-operator#basic-install. But the instructions don’t say what to do after the following command returns a URL:
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”
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”
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 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?
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:
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.
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!
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.
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)?
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, 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.
