Comments on: How to Install Ansible AWX on Kubernetes Cluster

By: Nekasas

Nekasas — Tue, 26 Sep 2023 11:02:17 +0000

Hi,

When I am trying to access AWX console it requires SSL certificate. How to bypass this?

By: Mainak

Mainak — Fri, 15 Sep 2023 08:10:06 +0000

i have followed the all the steps and all of my resources are running perfectly but still the AWX console dont come up…

FYI:- i am using k3s (rancher lightweight Kubernetes)

dont know what is going wrong 🙁

By: kyle jones

kyle jones — Thu, 14 Sep 2023 07:17:01 +0000

In reply to Jane.

Hello,

If you copied the exact commands, your PV configuration will be incorrect. Make sure the hostname matches the nodeaffinity. You can run this command to verify: kubectl get nodes –show-labels. Your server hostname is most likely not what the OP has posted.

By: Nick

Nick — Thu, 14 Sep 2023 00:04:38 +0000

Thank for a very clear step-by-step instruction, I have followed it for the latest version and seems everything running. However, I have noticed two svc created:

service/ansible-awx-service NodePort xxxxxxxx 80:31560/TCP 16m
service/ansible-awx-web-svc NodePort xxxxxxx 8052:32490/TCP 14m

which node-port should I used for the URL? I have tried both but neither of them responds, any suggestion to troubleshooting it?

By: Lucy

Lucy — Thu, 07 Sep 2023 12:17:16 +0000

In reply to Jane. Did you ever fix this? I'm running into the same problem

By: Keith

Keith — Tue, 29 Aug 2023 18:43:48 +0000

In reply to Bryan Vold. This is exactly why I'm trying to do. Are these the only two configuration files you needed? What about the PV?

By: Jane

Jane — Thu, 03 Aug 2023 18:17:29 +0000

I followed this post, but failed in step 4:
kubectl get pvc -n awx
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
postgres-13-ansible-awx-postgres-13-0 Pending local-storage 7m
kubectl get pods -n awx
NAME READY STATUS RESTARTS AGE
ansible-awx-postgres-13-0 0/1 Pending 0 2m19s
awx-operator-controller-manager-846fdb76d5-m5mbf 2/2 Running 4 (47m ago) 49m

By: Pradeep Kumar

Pradeep Kumar — Sun, 30 Jul 2023 04:56:54 +0000

In reply to Marshall. Hi Marshall, It seems like Kubernetes cluster is not reachable from the system on which you are trying run helm command. So, please try to fix connectivity issue first.

By: Marshall

Marshall — Fri, 28 Jul 2023 18:50:25 +0000

This helm install path no longer works.
helm install ansible-awx-operator awx-operator/awx-operator -n awx –create-namespace
Error: INSTALLATION FAILED: Kubernetes cluster unreachable: Get “http://localhost:8080/version”: dial tcp [::1]:8080: connect: connection refused

By: Bryan Vold

Bryan Vold — Tue, 25 Jul 2023 18:46:17 +0000

In reply to Pradeep Kumar.

Thanks for posting this. I was able to deploy AWX to my local Rancher Kubernetes setup.

I chose to use longhorn for storage, so I had to do things a bit differently.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: ansible-awx-projects
namespace: awx
spec:
accessModes:
– ReadWriteOnce
storageClassName: longhorn
resources:
requests:
storage: 1Gi

and then configured the internal Postgres limits:

apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
name: ansible-awx
namespace: awx
spec:
postgres_resource_requirements:
requests:
cpu: 500m
memory: 2Gi
limits:
cpu: ‘1’
memory: 4Gi
postgres_storage_requirements:
requests:
storage: 10Gi
limits:
storage: 50Gi
postgres_storage_class: longhorn
postgres_extra_args:
– ‘-c’
– ‘max_connections=1000’
projects_persistence: true
projects_existing_claim: ansible-awx-projects