Hi Team
I deployed awx-23.0.0 through awx-operator-2.5.2 in my k8s v1.30.2. I deployed ingress resources with tls hostname path in ngnix ingress controller with service type nodeport. everything working fine expect ingress. hostname is added in dns also.
When I try to access my awx through https:///#/login, I got refused to connect error msg in my browser.
Note : No issues in nodeport access. I can able to login using my nodeport.
Not sure what I missed in configuration. Please help me to fix this issue.
Here my detailed output of my deployment.
[kubeadmin@xl8phxc360awxtst ~]$ k get awx,all,ingress,secrets
NAME AGE
awx.awx.ansible.com/awx 19h
NAME READY STATUS RESTARTS AGE
pod/awx-operator-controller-manager-8598d95f75-vrbvl 2/2 Running 0 19h
pod/awx-postgres-13-0 1/1 Running 0 19h
pod/awx-task-6776dd5476-kmdgd 4/4 Running 0 19h
pod/awx-web-687448f856-pmgns 3/3 Running 0 19h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/awx-operator-controller-manager-metrics-service ClusterIP 10.110.1.23 8443/TCP 19h
service/awx-postgres-13 ClusterIP None 5432/TCP 19h
service/awx-service NodePort 10.102.52.102 80:30010/TCP 19h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/awx-operator-controller-manager 1/1 1 1 19h
deployment.apps/awx-task 1/1 1 1 19h
deployment.apps/awx-web 1/1 1 1 19h
NAME DESIRED CURRENT READY AGE
replicaset.apps/awx-operator-controller-manager-8598d95f75 1 1 1 19h
replicaset.apps/awx-task-6776dd5476 1 1 1 19h
replicaset.apps/awx-web-687448f856 1 1 1 19h
NAME READY AGE
statefulset.apps/awx-postgres-13 1/1 19h
NAME CLASS HOSTS ADDRESS PORTS AGE
ingress.networking.k8s.io/awx-ingress nginx xl8phxc360awxtst.ipengine360s1.net 10.109.44.45 80, 443 19h
NAME TYPE DATA AGE
secret/awx-admin-password Opaque 1 19h
secret/awx-app-credentials Opaque 3 19h
secret/awx-broadcast-websocket Opaque 1 19h
secret/awx-postgres-configuration Opaque 6 19h
secret/awx-receptor-ca kubernetes.io/tls 2 19h
secret/awx-receptor-work-signing Opaque 2 19h
secret/awx-secret-key Opaque 1 19h
secret/awx-secret-tls kubernetes.io/tls 2 19h
secret/redhat-operators-pull-secret Opaque 1 19h
[kubeadmin@xl8phxc360awxtst ~]$
My deployment yaml file as follows…
[kubeadmin@xl8phxc360awxtst base]$ cat awx.yaml
apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
name: awx
spec:
These parameters are designed for use with:
- AWX Operator: 2.0.0
awx-operator/README.md at 2.5.2 · ansible/awx-operator · GitHub
- AWX: 23.0.0
awx/INSTALL.md at 23.0.0 · ansible/awx · GitHub
admin_user: admin
admin_password_secret: awx-admin-password
service_type: nodeport
nodeport_port: 30010
ingress_type: ingress
ingress_class_name: nginx
ingress_tls_secret: awx-secret-tls
hostname: xl8phxc360awxtst.ipengine360s1.net
.
.
.
Below the error while accessing via hostname…
[kubeadmin@xl8phxc360awxtst ~]$ sudo curl -I xl8phxc360awxtst.ipengine360s1.net
curl: (7) Failed to connect to xl8phxc360awxtst.ipengine360s1.net port 80: Connection refused
[kubeadmin@xl8phxc360awxtst ~]$ sudo curl https://xl8phxc360awxtst.ipengine360s1.net
curl: (7) Failed to connect to xl8phxc360awxtst.ipengine360s1.net port 443: Connection refused
[kubeadmin@xl8phxc360awxtst ~]$
Through nodeport, it’s working…
[kubeadmin@xl8phxc360awxtst ~]$ sudo curl -I http://10.109.44.45:30010
HTTP/1.1 200 OK
Server: nginx
Date: Fri, 09 Aug 2024 12:54:23 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 1044
Connection: keep-alive
Vary: Accept-Language, Origin, Cookie
Content-Language: en
X-API-Total-Time: 0.072s
X-API-Request-Id: b4d22e1e38894cfba5d8a5538b162b65
Access-Control-Expose-Headers: X-API-Request-Id
Strict-Transport-Security: max-age=15768000
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
Cache-Control: no-cache, no-store, must-revalidate
Expires: 0
Pragma: no-cache
[kubeadmin@xl8phxc360awxtst ~]$