Completing the AWX Operator installation

979 views
Skip to first unread message

Terry Lemons

unread,
Jul 20, 2023, 12:14:41 PM7/20/23
to AWX Project
Hi

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:

# minikube service -n awx awx-demo-service --url
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 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

Thomas Plank

unread,
Jul 20, 2023, 2:59:27 PM7/20/23
to AWX Project
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. ;-)

Terry Lemons

unread,
Jul 21, 2023, 10:29:58 AM7/21/23
to AWX Project
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"
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           <none>        5432/TCP       23h
awx-demo-service       NodePort    10.102.50.41   <none>        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

Terry Lemons

unread,
Jul 21, 2023, 10:59:58 AM7/21/23
to AWX Project
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 |
| 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 |
|               |                                                 | https/443    | 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

Message has been deleted

Terry Lemons

unread,
Jul 26, 2023, 8:54:14 AM7/26/23
to AWX Project
Hi

Any suggestion on how the instructions in the demo aren't working in my environment?

Thanks

Terry Lemons

unread,
Jul 31, 2023, 4:00:22 PM7/31/23
to AWX Project
Hi

Any change to the installation instructions for AWX Operator 2.5.0?

Thanks
tl

AWX Project

unread,
Aug 2, 2023, 2:39:56 PM8/2/23
to AWX Project
are you having problems using operator 2.5? there is nothing special about 2.5 in terms of installation

AWX Team

Terry Lemons

unread,
Aug 2, 2023, 5:08:16 PM8/2/23
to AWX Project
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, clicked on 'Basic Install' as I did before, and now get a 404 File not found error.




AWX Project

unread,
Aug 4, 2023, 1:32:47 PM8/4/23
to AWX Project
we were changing around the links yesterday, should work now https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md

Terry Lemons

unread,
Aug 8, 2023, 3:08:16 PM8/8/23
to AWX Project
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 and then in 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. 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

Terry Lemons

unread,
Aug 11, 2023, 11:50:03 AM8/11/23
to AWX Project
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!

Gertz

unread,
Aug 11, 2023, 12:08:40 PM8/11/23
to AWX Project
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
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 napsal:

Terry Lemons

unread,
Sep 5, 2023, 2:47:44 PM9/5/23
to AWX Project
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, 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
---
apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
  name: awx-demo
spec:
  service_type: nodeport

ldpdd042:/tmp #

I'm not sure where the problem is.  Thanks for your thoughts!

Wei-Yen Tan

unread,
Sep 5, 2023, 2:49:32 PM9/5/23
to awx-p...@googlegroups.com
You used awx-demo. Not awx-demo-task-6d7b6489d-zrcqx

Sent from Outlook for iOS
From: 'Terry Lemons' via AWX Project <awx-p...@googlegroups.com>
Sent: Wednesday, September 6, 2023 6:47:43 AM
To: AWX Project <awx-p...@googlegroups.com>
Subject: [awx-project] Re: Completing the AWX Operator installation
 
--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/awx-project/76aacd00-2496-4477-8aec-fa43acad5f3fn%40googlegroups.com.

Lemons, Terry

unread,
Sep 5, 2023, 3:00:07 PM9/5/23
to awx-p...@googlegroups.com

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

From: awx-p...@googlegroups.com <awx-p...@googlegroups.com> On Behalf Of Wei-Yen Tan
Sent: Tuesday, September 5, 2023 2:49 PM
To: awx-p...@googlegroups.com
Subject: Re: [awx-project] Re: Completing the AWX Operator installation

 

[EXTERNAL EMAIL]

You used awx-demo. Not awx-demo-task-6d7b6489d-zrcqx

From: 'Terry Lemons' via AWX Project <awx-p...@googlegroups.com>
Sent: Wednesday, September 6, 2023 6:47:43 AM
To: AWX Project <awx-p...@googlegroups.com>
Subject: [awx-project] Re: Completing the AWX Operator installation

 

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 [github.com], 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
---
apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
  name: awx-demo
spec:
  service_type: nodeport

ldpdd042:/tmp #

 

I'm not sure where the problem is.  Thanks for your thoughts!

On Friday, August 11, 2023 at 12:08:40 PM UTC-4 Gertz wrote:

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.


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 napsal:

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!

On Tuesday, August 8, 2023 at 3:08:16 PM UTC-4 Terry Lemons wrote:

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 [github.com] and then in https://github.com/ansible/awx-operator/blob/devel/docs/installation/basic-install.md [github.com]; all went well. I then moved on to the demo at https://asciinema.org/a/416946 [asciinema.org]. 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

On Friday, August 4, 2023 at 1:32:47 PM UTC-4 AWX Project wrote:

On Wednesday, August 2, 2023 at 5:08:16 PM UTC-4 terry....@dell.com wrote:

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 [github.com], clicked on 'Basic Install' as I did before, and now get a 404 File not found error.

 

 

 

On Wednesday, August 2, 2023 at 2:39:56 PM UTC-4 AWX Project wrote:

are you having problems using operator 2.5? there is nothing special about 2.5 in terms of installation

 

AWX Team

On Monday, July 31, 2023 at 4:00:22 PM UTC-4 terry....@dell.com wrote:

Hi

 

Any change to the installation instructions for AWX Operator 2.5.0?

 

Thanks

tl

On Wednesday, July 26, 2023 at 8:54:14 AM UTC-4 Terry Lemons wrote:

Hi

 

Any suggestion on how the instructions in the demo aren't working in my environment?

 

Thanks

 

On Friday, July 21, 2023 at 10:59:58 AM UTC-4 Terry Lemons wrote:

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 [192.168.49.2] |


| 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 [192.168.49.2] |
|               |                                                 | https/443    | http://192.168.49.2:32371 [192.168.49.2] |


| 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

On Friday, July 21, 2023 at 10:29:58 AM UTC-4 Terry Lemons wrote:

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:


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


NAME                   TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)        AGE
awx-demo-postgres-13   ClusterIP   None           <none>        5432/TCP       23h
awx-demo-service       NodePort    10.102.50.41   <none>        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

On Thursday, July 20, 2023 at 2:59:27 PM UTC-4 tplan...@gmail.com wrote:

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. ;-)

terry....@dell.com schrieb am Donnerstag, 20. Juli 2023 um 18:14:41 UTC+2:

Hi

 

I've followed the excellent and detailed instructions for installing AWX Operator at https://github.com/ansible/awx-operator#basic-install [github.com]. But the instructions don't say what to do after the following command returns a URL:

 

# minikube service -n awx awx-demo-service --url

 

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 https://github.com/ansible/awx [github.com], I see a link to the Red Hat Tower site. Is that the correct place for AWX getting started information?

 

Thanks!

tl

--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.

Wei-Yen Tan

unread,
Sep 5, 2023, 3:02:22 PM9/5/23
to awx-p...@googlegroups.com
What is your goal. What are you trying to achieve? 

Sent from Outlook for iOS
From: 'Lemons, Terry' via AWX Project <awx-p...@googlegroups.com>
Sent: Wednesday, September 6, 2023 6:59:56 AM
To: awx-p...@googlegroups.com <awx-p...@googlegroups.com>
Subject: RE: [awx-project] Re: Completing the AWX Operator installation
 

Lemons, Terry

unread,
Sep 5, 2023, 3:55:56 PM9/5/23
to awx-p...@googlegroups.com

I want to install AWX and use it to manage my team’s Ansible activities via its UI.

 

 

Internal Use - Confidential

From: awx-p...@googlegroups.com <awx-p...@googlegroups.com> On Behalf Of Wei-Yen Tan
Sent: Tuesday, September 5, 2023 3:02 PM
To: awx-p...@googlegroups.com
Subject: Re: [awx-project] Re: Completing the AWX Operator installation

 

[EXTERNAL EMAIL]

What is your goal. What are you trying to achieve? 

--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.

Wei-Yen Tan

unread,
Sep 5, 2023, 3:56:56 PM9/5/23
to awx-p...@googlegroups.com
No I mean why are you executing into containers. There should be no need for that

Sent from Outlook for iOS
From: 'Lemons, Terry' via AWX Project <awx-p...@googlegroups.com>
Sent: Wednesday, September 6, 2023 7:55:46 AM

Lemons, Terry

unread,
Sep 5, 2023, 4:01:02 PM9/5/23
to awx-p...@googlegroups.com

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.

 

Thanks

 

 

Internal Use - Confidential

From: awx-p...@googlegroups.com <awx-p...@googlegroups.com> On Behalf Of Wei-Yen Tan
Sent: Tuesday, September 5, 2023 3:57 PM
To: awx-p...@googlegroups.com
Subject: Re: [awx-project] Re: Completing the AWX Operator installation

 

[EXTERNAL EMAIL]

No I mean why are you executing into containers. There should be no need for that

--
You received this message because you are subscribed to a topic in the Google Groups "AWX Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/awx-project/TDdWikEYwK8/unsubscribe [groups.google.com].
To unsubscribe from this group and all its topics, send an email to awx-project...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/awx-project/SYBP282MB352562BB93DC2CD11BBDE966ADE8A%40SYBP282MB3525.AUSP282.PROD.OUTLOOK.COM [groups.google.com].

Wei-Yen Tan

unread,
Sep 5, 2023, 4:02:58 PM9/5/23
to awx-p...@googlegroups.com
Did you create a node port or ingress 

Sent from Outlook for iOS
From: 'Lemons, Terry' via AWX Project <awx-p...@googlegroups.com>
Sent: Wednesday, September 6, 2023 8:00:44 AM

Lemons, Terry

unread,
Sep 5, 2023, 4:06:46 PM9/5/23
to awx-p...@googlegroups.com

I only did what was in the instructions. Here’s the output from a couple of commands:

ldpdd042:~ # kubectl get pods -n awx

NAME                                               READY   STATUS    RESTARTS   AGE

awx-demo-postgres-13-0                             1/1     Running   0          115m

awx-demo-task-6d7b6489d-zrcqx                      4/4     Running   0          114m

awx-demo-web-7b96744696-hl4sp                      3/3     Running   0          113m

awx-operator-controller-manager-65ddfcbf7d-j4nzf   2/2     Running   0          120m

ldpdd042:~ # kubectl get svc -n awx -l "app.kubernetes.io/managed-by=awx-operator"

NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE

awx-demo-postgres-13   ClusterIP   None             <none>        5432/TCP       116m

awx-demo-service       NodePort    10.100.136.234   <none>        80:31829/TCP   115m

ldpdd042:~ #

 

Does this information answer your question?

 

 

Internal Use - Confidential

From: awx-p...@googlegroups.com <awx-p...@googlegroups.com> On Behalf Of Wei-Yen Tan
Sent: Tuesday, September 5, 2023 4:03 PM
To: awx-p...@googlegroups.com
Subject: Re: [awx-project] Re: Completing the AWX Operator installation

 

[EXTERNAL EMAIL]

Did you create a node port or ingress 

From: 'Lemons, Terry' via AWX Project <awx-p...@googlegroups.com>
Sent: Wednesday, September 6, 2023 8:00:44 AM
To: awx-p...@googlegroups.com <awx-p...@googlegroups.com>
Subject: RE: [awx-project] Re: Completing the AWX Operator installation

 

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 [github.com], 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.

--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.

Wei-Yen Tan

unread,
Sep 5, 2023, 4:08:18 PM9/5/23
to awx-p...@googlegroups.com
Go to this address 


Sent from Outlook for iOS
From: 'Lemons, Terry' via AWX Project <awx-p...@googlegroups.com>
Sent: Wednesday, September 6, 2023 8:06:35 AM

Lemons, Terry

unread,
Sep 5, 2023, 4:20:58 PM9/5/23
to awx-p...@googlegroups.com

That IP address does not respond to a ping, even within the server where I’m running AWX.

 

 

Internal Use - Confidential

From: awx-p...@googlegroups.com <awx-p...@googlegroups.com> On Behalf Of Wei-Yen Tan
Sent: Tuesday, September 5, 2023 4:08 PM
To: awx-p...@googlegroups.com
Subject: Re: [awx-project] Re: Completing the AWX Operator installation

 

[EXTERNAL EMAIL]

--
You received this message because you are subscribed to a topic in the Google Groups "AWX Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/awx-project/TDdWikEYwK8/unsubscribe [groups.google.com].
To unsubscribe from this group and all its topics, send an email to awx-project...@googlegroups.com.

Wei-Yen Tan

unread,
Sep 5, 2023, 4:22:53 PM9/5/23
to awx-p...@googlegroups.com
Sorry navigate to that server ip address with that port

Sent from Outlook for iOS
From: 'Lemons, Terry' via AWX Project <awx-p...@googlegroups.com>
Sent: Wednesday, September 6, 2023 8:20:42 AM

Lemons, Terry

unread,
Sep 5, 2023, 4:32:54 PM9/5/23
to awx-p...@googlegroups.com

Hi Wei-Yen

 

Thanks for this help.

 

Logged into the system where I’ve installed AWX Operator, I execute the ‘kubectl get svc’ command and it shows me a cluster IP address and TCP ports. I can’t ping that cluster-ip address, even from the system where I’ve installed AWX Operator. Looking at the IP addresses available on this system, I don’t see 10.100.136.234 anywhere.  So I don’t see any way to make a connection to the AWX instance running in the Kubernetes cluster. Is there supposed to be an ‘external-ip’ value?

 

Thoughts?

 

Thanks

tl

 

ldpdd042:~ # kubectl get svc -n awx -l "app.kubernetes.io/managed-by=awx-operator"

NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE

awx-demo-postgres-13   ClusterIP   None             <none>        5432/TCP       138m

awx-demo-service       NodePort    10.100.136.234   <none>        80:31829/TCP   138m

ldpdd042:~ # ping -c 1 10.100.136.234

PING 10.100.136.234 (10.100.136.234) 56(84) bytes of data.

^C

--- 10.100.136.234 ping statistics ---

1 packets transmitted, 0 received, 100% packet loss, time 0ms

 

ldpdd042:~ # ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

       valid_lft forever preferred_lft forever

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

    link/ether 00:50:56:9d:3f:16 brd ff:ff:ff:ff:ff:ff

    altname enp11s0

    altname ens192

    inet 10.247.229.42/21 brd 10.247.231.255 scope global eth0

       valid_lft forever preferred_lft forever

    inet6 fe80::250:56ff:fe9d:3f16/64 scope link

       valid_lft forever preferred_lft forever

3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default

    link/ether 02:42:15:ba:76:42 brd ff:ff:ff:ff:ff:ff

    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0

       valid_lft forever preferred_lft forever

    inet6 fe80::42:15ff:feba:7642/64 scope link

       valid_lft forever preferred_lft forever

4: br-00efee37fdbd: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default

    link/ether 02:42:01:5f:b4:0d brd ff:ff:ff:ff:ff:ff

    inet 192.168.49.1/24 brd 192.168.49.255 scope global br-00efee37fdbd

       valid_lft forever preferred_lft forever

    inet6 fe80::42:1ff:fe5f:b40d/64 scope link

       valid_lft forever preferred_lft forever

10: vethf7c05f0@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-00efee37fdbd state UP group default

    link/ether 86:65:c3:65:bc:b9 brd ff:ff:ff:ff:ff:ff link-netnsid 0

    inet6 fe80::8465:c3ff:fe65:bcb9/64 scope link

       valid_lft forever preferred_lft forever

ldpdd042:~ #

 

 

Internal Use - Confidential

From: awx-p...@googlegroups.com <awx-p...@googlegroups.com> On Behalf Of Wei-Yen Tan
Sent: Tuesday, September 5, 2023 4:23 PM
To: awx-p...@googlegroups.com
Subject: Re: [awx-project] Re: Completing the AWX Operator installation

 

[EXTERNAL EMAIL]

Sorry navigate to that server ip address with that port

--
You received this message because you are subscribed to a topic in the Google Groups "AWX Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/awx-project/TDdWikEYwK8/unsubscribe [groups.google.com].
To unsubscribe from this group and all its topics, send an email to awx-project...@googlegroups.com.

Wei-Yen Tan

unread,
Sep 5, 2023, 4:34:15 PM9/5/23
to awx-p...@googlegroups.com
What's your server ip. Navigate to that with the node port

Sent from Outlook for iOS
From: 'Lemons, Terry' via AWX Project <awx-p...@googlegroups.com>
Sent: Wednesday, September 6, 2023 8:32:36 AM

Lemons, Terry

unread,
Sep 5, 2023, 4:43:54 PM9/5/23
to awx-p...@googlegroups.com

Given this information:

 

ldpdd042:~ # kubectl get svc -n awx -l "app.kubernetes.io/managed-by=awx-operator"

NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE

awx-demo-postgres-13   ClusterIP   None             <none>        5432/TCP       149m

awx-demo-service       NodePort    10.100.136.234   <none>        80:31829/TCP   148m

ldpdd042:~ #

 

ldpdd042:~ # ip address show dev eth0

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

    link/ether 00:50:56:9d:3f:16 brd ff:ff:ff:ff:ff:ff

    altname enp11s0

    altname ens192

    inet 10.247.229.42/21 brd 10.247.231.255 scope global eth0

       valid_lft forever preferred_lft forever

    inet6 fe80::250:56ff:fe9d:3f16/64 scope link

       valid_lft forever preferred_lft forever

ldpdd042:~ #

 

I thought I’d be able to connect to http://10.247.229.42:80 to access the AWX UI. But I get ‘This site can’t be reached’ when I try to connect via a web browser.

 

What am I missing?

 

 

 

Internal Use - Confidential

From: awx-p...@googlegroups.com <awx-p...@googlegroups.com> On Behalf Of Wei-Yen Tan
Sent: Tuesday, September 5, 2023 4:34 PM
To: awx-p...@googlegroups.com
Subject: Re: [awx-project] Re: Completing the AWX Operator installation

 

[EXTERNAL EMAIL]

What's your server ip. Navigate to that with the node port

--
You received this message because you are subscribed to the Google Groups "AWX Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to awx-project...@googlegroups.com.

Lemons, Terry

unread,
Sep 6, 2023, 11:30:02 AM9/6/23
to awx-p...@googlegroups.com

Hi

 

I ignored the AWX demo step involving ‘kubectl exec, as these don’t work with the current AWX operator release. But I was able to complete the rest of the steps in the demo. I can complete a curl command, run within the server, to the AWX API.

 

But, how can I complete a http/https call from a web browser running OUTSIDE of the AWX server? What does the mapping between an inbound http/https request and the AWX process running in the Kubernetes cluster?

 

Thanks

 

 

Internal Use - Confidential

From: 'Lemons, Terry' via AWX Project <awx-p...@googlegroups.com>
Sent: Tuesday, September 5, 2023 4:44 PM
To: awx-p...@googlegroups.com
Subject: RE: [awx-project] Re: Completing the AWX Operator installation

 

[EXTERNAL EMAIL]

Given this information:

 

ldpdd042:~ # kubectl get svc -n awx -l "app.kubernetes.io/managed-by=awx-operator"

NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE

awx-demo-postgres-13   ClusterIP   None             <none>        5432/TCP       149m

awx-demo-service       NodePort    10.100.136.234   <none>        80:31829/TCP   148m

ldpdd042:~ #

 

ldpdd042:~ # ip address show dev eth0

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

    link/ether 00:50:56:9d:3f:16 brd ff:ff:ff:ff:ff:ff

    altname enp11s0

    altname ens192

    inet 10.247.229.42/21 brd 10.247.231.255 scope global eth0

       valid_lft forever preferred_lft forever

    inet6 fe80::250:56ff:fe9d:3f16/64 scope link

       valid_lft forever preferred_lft forever

ldpdd042:~ #

 

I thought I’d be able to connect to http://10.247.229.42:80 [10.247.229.42] to access the AWX UI. But I get ‘This site can’t be reached’ when I try to connect via a web browser.

Wei-Yen Tan

unread,
Sep 10, 2023, 7:18:26 PM9/10/23
to awx-p...@googlegroups.com
Yoy have a node port connection. So connect to the server ip address https://10.247.229.42:31829

Sent from Outlook for iOS
From: 'Lemons, Terry' via AWX Project <awx-p...@googlegroups.com>
Sent: Thursday, September 7, 2023 3:29:43 AM

Terry Lemons

unread,
Sep 11, 2023, 4:53:44 PM9/11/23
to AWX Project
Thanks for the suggestion, but connecting to  ip address https://10.247.229.42:31829 via a web browser yields:

This site can’t be reached

10.247.229.42 refused to connect.


which makes sense, because nothing is providing a service to external-to-this-server connections to tcp port 31829.

Thoughts?  Thanks! 

On Sunday, September 10, 2023 at 7:18:26 PM UTC-4 weiye...@gmail.com wrote:
Yoy have a node port connection. So connect to the server ip address https://10.247.229.42:31829

Sent from Outlook for iOS
Reply all
Reply to author
Forward
0 new messages