# Installing AWX on minicube vs compose **URL:** \ **Category:** AWX Project\ **Tags:** kubernetes, awx\ **Created:** [March 31, 2021, 8:48am UTC](https://forum.ansible.com/t/installing-awx-on-minicube-vs-compose/34894 "2021-03-31T08:48:19Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Hrvoje\_Gaspar](https://avatars.discourse-cdn.com/v4/letter/h/3ab097/32.png) [@Hrvoje\_Gaspar](https://forum.ansible.com/u/Hrvoje_Gaspar)\ **Post date:** [March 31, 2021, 8:48am UTC](https://forum.ansible.com/t/installing-awx-on-minicube-vs-compose/34894/1 "2021-03-31T08:48:19Z")
Hi guys and gals, I was somewhat surprised to find out that operator is now the only supported installation method for awx. Most of environments I’ve installed AWX in so far have been docker-compose based. According to the documentation, compose should be only used for non production environments, and yet minikube is mentioned as a quick way to bring up awx operator. Is minikube really a better solution to run awx in prod environments? Compose was a perfect solution for environments with limited resources that are unable to provision a kubernetes cluster. With minikube I’m somewhat worried about data persistance, as it is specifically intended to be a learning and testing tool, and not a production ready kubernetes instance. What are your thoughts on this? Is minikube stable enough to run production awx instance? ---
**Author:** ![Nuno\_Jordao](https://avatars.discourse-cdn.com/v4/letter/n/a4c791/32.png) [@Nuno\_Jordao](https://forum.ansible.com/u/Nuno_Jordao)\ **Post date:** [March 31, 2021, 1:32pm UTC](https://forum.ansible.com/t/installing-awx-on-minicube-vs-compose/34894/2 "2021-03-31T13:32:24Z")
Hello, In my opinion they just want to force us, who don’t have kubernettes, to buy Tower. They save on docker-compose development and bring more revenue. If not, we need to had another unecessary layer of complexity with minikube. Better yet, for them, with Openshift. It is similar to the CentOS changes… BTW, it is not RedHat anymore, it’s IBM… ---
**Author:** ![jpmens1](https://avatars.discourse-cdn.com/v4/letter/j/e9c0ed/32.png) [@jpmens1](https://forum.ansible.com/u/jpmens1)\ **Post date:** [March 31, 2021, 1:47pm UTC](https://forum.ansible.com/t/installing-awx-on-minicube-vs-compose/34894/3 "2021-03-31T13:47:39Z")
> In my opinion they just want to force us, who don’t have kubernettes, to buy Tower. I just saw a talk by a Red Hat employee that the product we used to know as “Tower” will no longer exist. It’s all going to containers. Quite the watch: [https://www.youtube.com/watch?v=jZEXx8FgR58&t=2391s](https://www.youtube.com/watch?v=jZEXx8FgR58&t=2391s) -JP ---
**Author:** ![Hrvoje\_Gaspar](https://avatars.discourse-cdn.com/v4/letter/h/3ab097/32.png) [@Hrvoje\_Gaspar](https://forum.ansible.com/u/Hrvoje_Gaspar)\ **Post date:** [March 31, 2021, 1:56pm UTC](https://forum.ansible.com/t/installing-awx-on-minicube-vs-compose/34894/4 "2021-03-31T13:56:42Z")
_In my opinion they just want to force us, who don’t have kubernettes, to buy Tower. They save on docker-compose development and bring more revenue._ I don’t think that is the case. If that is the case, that logic is flawed. If a potential client is bent on using free open source technology and can afford ansible tower, they most likely have enough resources (or can invest in enough resources) to create a kubernetes cluster, or even to use okd if we wanna keep it in red hat family, and provision AWX operator there. I don’t mind paying for Tower and for support, but there is a large number of potential clients who are not large enough to be able to afford that. And they are now left hanging, because they won’t be able to keep updating AWX to new releases. I started playing with provisioning AWX on minikube today, and there is a plethora of massive issues if one plans to use it for production. And for a company that used AWX, maybe not so much for automation, as that can easily be done with just Ansible, but for access conrolled task delegation in order to refocus their core operations teams from basic everyday repetative tasks to more important problems, that is a big loss. I don’t think that the issue is so much with them trying to force people to buy Ansible Tower, as much as it’s them trying to refocus their stengths to building new Tower features, as Tower will change massively in the nearer future. _I just saw a talk by a Red Hat employee that the product we used to know as “Tower” will no longer exist. It’s all going to containers. Quite the watch: [https://www.youtube.com/watch?v=jZEXx8FgR58&t=2391s](https://www.youtube.com/watch?v=jZEXx8FgR58&t=2391s)_ I’ve heard about this. I like the course they’re taking with the whole automation platform. Dana srijeda, 31. ožujka 2021. u 15:32:53 UTC+2 korisnik [nuno....@gmail.com](mailto:nuno....@gmail.com) napisao je: ---
**Author:** ![klaasdemter](https://avatars.discourse-cdn.com/v4/letter/k/3bc359/32.png) [@klaasdemter](https://forum.ansible.com/u/klaasdemter)\ **Post date:** [March 31, 2021, 2:08pm UTC](https://forum.ansible.com/t/installing-awx-on-minicube-vs-compose/34894/5 "2021-03-31T14:08:32Z")
Hi, I am now using k3s under centos 8.3 for awx tests. This was fairly easy. Only encountered one issue: [https://github.com/k3s-io/k3s/issues/3122](https://github.com/k3s-io/k3s/issues/3122) Using the operator with ingress for http(s), but I am not using it for anything serious yet - just for playing around with AWX ui/api so I am not sure how well it actually works if you get users/jobs on there 🙂 Greetings Klaas ---
**Author:** ![Wei-Yen\_Tan](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wei-yen_tan/32/4111_2.png) [@Wei-Yen\_Tan](https://forum.ansible.com/u/Wei-Yen_Tan)\ **Post date:** [April 5, 2021, 7:58am UTC](https://forum.ansible.com/t/installing-awx-on-minicube-vs-compose/34894/6 "2021-04-05T07:58:00Z")
I just use rancher and kubernetes. Install was seemless. Had to use an external database. but was straightforward