# Deploy AWX on 3-Node Cluster **URL:** \ **Category:** Get Help\ **Tags:** documentation, ubuntu, awx, kubernetes\ **Created:** [April 30, 2024, 4:53pm UTC](https://forum.ansible.com/t/deploy-awx-on-3-node-cluster/5225 "2024-04-30T16:53:13Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\ **Post date:** [May 1, 2024, 12:31pm UTC](https://forum.ansible.com/t/deploy-awx-on-3-node-cluster/5225/2 "2024-05-01T12:31:07Z")
> [@Novasyll](#): > > I struggled to deploy AWX on it since microk8s seems have some specialities in it. Hi, what were the actual problems for you to deploy AWX on microk8s? If your storage provisioner, ingress controller, and load balancer are configured correctly, there are less differences between deploying on single node cluster and deploying on multi nodes cluster. Sorry if this is a stupid recommendation but before deploying AWX Operator and AWX, I recommend you to test your cluster with minimal web app by some steps like this, to ensure your LB and ingress work as expected: [Question about adding remote EE node to AWX k8s cluster - #9 by kurokobo](http://forum.ansible.com/t/question-about-adding-remote-ee-node-to-awx-k8s-cluster/4951/9) > [@Novasyll](#): > > They all mounted an NFS export (/data) from another NFS VM (also Ubuntu). So my idea is to let AWX/K8S access the storage via host-path. This should work, but if you are interested in more native way in K8s, you can create `nfs` based PV instead of `hostPath` based one: [Persistent Volumes | Kubernetes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistent-volumes). Also there are good CSI for NFS: [https://microk8s.io/docs/how-to-nfs](https://microk8s.io/docs/how-to-nfs) --- _[View the full topic](https://forum.ansible.com/t/deploy-awx-on-3-node-cluster/5225)._