Completing the AWX Operator installation

Archives AWX Project
21

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 5432/TCP 116m

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

ldpdd042:~ #

Does this information answer your question?

Internal Use - Confidential

22

Go to this address

Http://10.100.136.234:31829

23

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

Internal Use - Confidential

24

Sorry navigate to that server ip address with that port

25

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 5432/TCP 138m

awx-demo-service NodePort 10.100.136.234 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

26

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

27

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 5432/TCP 149m

awx-demo-service NodePort 10.100.136.234 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

28

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

29

Yoy have a node port connection. So connect to the server ip address https://10.247.229.42:31829

30

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!