I’ve been using AWX since version 3.0.0 with local docker which is easy to manage but since development moved to kubernetes I’ve been struggling to configure AWX correctly.
I’ve searched github, stackoverflow and google but found no useful guide that shows how to implement https with custom certificate in regards to AWX and minikube.
The official operator documentation briefly shows a ingress and loadbalancer configuration but nothing about what to do in detail.
I’m not sure of your specific use case, but from what I gather from your configuration and attempt to port forward you need the AWX deployment to be accessible beyond the localhost. I have seen guides on forwarding a minikube deployment to a remote host, but, as I understand it, at the end of the day you end up with a minikube deployment which is only locally accessible from the remote host. Rather than fighting the intention of the build, I would recommend deploying in K3S. This will have a single node cluster up and running in a few seconds. This provides you with the same ease of use as minikube, but with the ability to have something functional at the end of the process. This guides is very helpful and should have you up and running in a couple of minutes https://github.com/kurokobo/awx-on-k3s . As a side note I built my ingress through kubernetes. If you wish to do the same simply leave out the ingress parameters in your awx configuration or set the ingress type to none, then build an external ingress according to Kubernetes documentation with your backend set to the awx service. I hope this is helpful. If you really want to stick with minikube, let me know and I will try to track down that documentation for you.
Thanks for posting Kurokobo’s github repo. I’ve create a demo video on YouTube that follows Kurokobo’s walkthrough with just a couple of additions. It’s a great piece of work and will help a lot of people so thanks! I give full credit to Kurokobo in the video and added his GitHub repo to the Gist.