How to install AWX using the awx-operator – Centos8 + K3s + HTTPS (single node cluster)
Install the awx-operator on Centos 8 using K3s + HTTPS.
Follow along using this Gist containing all the commands and links I’ve used in this demo:
https://gist.github.com/dmccuk/098fccc488c8a5aeaa5f859855660018
Thanks to Kurokobo for creating the walkthrough. GitHub page: https://github.com/kurokobo/awx-on-k3s
If you get any issues or questions, leave them in the comments.
If you want other Demo video’s made, let me know in the comments with details on what you want me to cover.
centos 8
Thanks so much for this, I was struggling to get the new AWX working with HTTPS, and this worked for me.
Im getting reconsiler error at the end of deployment can you help me
Hello Dennis
first of all good job to summarize how to do it
One question : how can we apply/adapt your procedure to an existing running awx operator instance in k3s cluster ?
Thanks for your feedback
Thank you for this. I tried using your aproach and it didn't work for me in 2023. Then I tried kurokobo manual usuing your advices and now I have working https instance. Hope it will help somebody.
Thanks for sharing, seems a lot less struggle than via the AWX owns install method which I find cumbersome and badly documented.
Thank you very much for these lovely tutorials, I'm trying it but below command failing with error, Please help.
[ansible@awx awx-on-k3s]$ k3s kubectl apply -k base
persistentvolume/awx-postgres-volume created
persistentvolume/awx-projects-volume created
Error from server (NotFound): error when creating "base": namespaces "awx" not found
Error from server (NotFound): error when creating "base": namespaces "awx" not found
Error from server (NotFound): error when creating "base": namespaces "awx" not found
Error from server (NotFound): error when creating "base": namespaces "awx" not found
Error from server (NotFound): error when creating "base": namespaces "awx" not found
Error from server (NotFound): error when creating "base": namespaces "awx" not found
Did my comment get deleted? lmao…
#Second
How to Fix This
[ans@localhost awx-on-k3s]$ sudo mkdir -p /data/postgres
[ans@localhost awx-on-k3s]$ sudo mkdir -p /data/projects
[ans@localhost awx-on-k3s]$ sudo chown 1000:0 /data/projects
[ans@localhost awx-on-k3s]$ k3s kubectl apply -k base
persistentvolume/awx-postgres-volume created
persistentvolume/awx-projects-volume created
Error from server (NotFound): error when creating "base": namespaces "awx" not found
Error from server (NotFound): error when creating "base": namespaces "awx" not found
Error from server (NotFound): error when creating "base": namespaces "awx" not found
Error from server (NotFound): error when creating "base": namespaces "awx" not found
Error from server (NotFound): error when creating "base": namespaces "awx" not found
Error from server (NotFound): error when creating "base": namespaces "awx" not found
[ans@localhost awx-on-k3s]$
Hi @LondonIAC this is great. Could you do a first experiences or tutorial with using AWX, or maybe even how you import an existing ansible deployment into AWX to switch from ansible per CLI to GUI infra management?
has anyone used k8s cluster for awx deployment ? please share steps for awx 0.20.0 on k8s
Hi, can you provide a video with a fresh awx installation on a azure kubernetes cluster?
Thanks for the video Sir! but seems there is an issue on the pvc.yaml file where volume-claim was just on "pending" status while all PV are in "bound" status.
It would be great to see a ubuntu version of this configuration
For me that not pretty good : localhost : ok=32 changed=0 unreachable=0 failed=1 skipped=25 rescued=0 ignored=0 is always failling in VM… 🙁
Hello! Great video 🙂 I have have been trying to find the best solution to install awx-operator on my centOS vm. So far i have liked the k3s deployment most. Small question – do you have some tips how can i upgrade my awx-operator, if there will be a newer version out ?
Hello! Thanks for the video. I can't resolve an issue. After kubectl apply, my pod remains in the following status:
k3s kubectl get pod
NAME READY STATUS RESTARTS AGE
awx-operator-69c646c48f-fbw4g 0/1 ImagePullBackOff 0 3m16s
It seems that it cannot pull the image. Any ideas on how I should resolve this?
Thanks,
Liviu