" Install kubernetes directly on a machine. Not minikube.
Minikube is for development or experiments.
Try K0s or K3s. They are small and simple enough to get going then you can
install AWX on top of that."
Thanks for this suggestion. I followed the 'formal' AWX installation documentation at
https://github.com/ansible/awx-operator/tree/devel/docs/installation, which specifies/suggests the use of minikube. Given minikube's limitations, may I suggest that recommending minikube with AWX is a terrible idea, because it does not support use of the AWX UI via a web interface? This is what I've been trying to achieve for weeks, and have wasted time trying to get the minikube-based deployment to work. Would someone please update the documentation, replacing minikube with a better kubernetes option?
"Hi Terry,
The README takes you through the steps to get the process up and running.
The main thing to bear in mind is that you need to change all references to '
awx.example.com' to a fully qualified domain name that resolves to the IP address of the server you installing k3s on.
The other thing to remember is that when you stop the k3s service the containers are not torn down.
You need to run a script called k3s-killall.sh to do that.
This may have been fixed in a more recent version to what I'm running.
Hope this helps."
This was a HUGE help. Thank you SO MUCH for making me aware of this option. I followed the instructions and ended up with a working environment in minutes. I wish that I had been aware of this option when I started investigating AWX in August. Would it be possible to add this deployment option to the AWX documentation, so others can easily find it? Thanks again!
On Thursday, October 19, 2023 at 11:10:55 AM UTC-4 AWX Project wrote:
@terry. That's how you expose services from kubernetes.