# Limit AWX Operator and instances installation to a given namespace

**URL:** <https://forum.ansible.com/t/limit-awx-operator-and-instances-installation-to-a-given-namespace/35741>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [September 15, 2021, 1:50pm UTC](https://forum.ansible.com/t/limit-awx-operator-and-instances-installation-to-a-given-namespace/35741 "2021-09-15T13:50:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cnu\_k](https://avatars.discourse-cdn.com/v4/letter/c/a88e4f/32.png) [@Cnu\_k](https://forum.ansible.com/u/Cnu_k)\
**Post date:** [September 15, 2021, 1:50pm UTC](https://forum.ansible.com/t/limit-awx-operator-and-instances-installation-to-a-given-namespace/35741/1 "2021-09-15T13:50:22Z")

</div>

Hi,

Going through AWX Operator and posts it appears that the operator installs CR/CRDs into ‘default’ namespace by default. I believe it’s possible to create AWX instance in a different namespace after that.  
Would like to know how to limit the operator and instance to a specific namespace as we don’t allow any dev teams to use the default namespace, avoid that route if possible.  
I saw few PRs and posts but not clear on the timeline when this feature will be released.  
Let me know if anyone has come across any manual configuration to make that work until we have an official approach from AWX team.

Thanks

---

<div class="post-metadata">

**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:** [September 15, 2021, 1:57pm UTC](https://forum.ansible.com/t/limit-awx-operator-and-instances-installation-to-a-given-namespace/35741/2 "2021-09-15T13:57:25Z")

</div>

I actually found a kustomize github repository that installs it in awx namespace

[https://github.com/kurokobo/awx-on-k3s](https://github.com/kurokobo/awx-on-k3s)

Have a look at the kustomize yaml file that you can deploy to any cluster (will work even if it is not k3s) just need a modern kubernetes cluster

---

<div class="post-metadata">

**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:** [September 15, 2021, 2:54pm UTC](https://forum.ansible.com/t/limit-awx-operator-and-instances-installation-to-a-given-namespace/35741/3 "2021-09-15T14:54:20Z")

</div>

[https://github.com/kurokobo/awx-on-k3s/blob/main/base/kustomization.yaml](https://github.com/kurokobo/awx-on-k3s/blob/main/base/kustomization.yaml)

Look at this for a fuller example with the namespace

---

<div class="post-metadata">

**Author:** ![Cnu\_k](https://avatars.discourse-cdn.com/v4/letter/c/a88e4f/32.png) [@Cnu\_k](https://forum.ansible.com/u/Cnu_k)\
**Post date:** [September 15, 2021, 3:32pm UTC](https://forum.ansible.com/t/limit-awx-operator-and-instances-installation-to-a-given-namespace/35741/4 "2021-09-15T15:32:06Z")

</div>

Thank you very much. I was looking at that git repo but didn’t get to all details, this is helpful to keep all custom configuration in one or more files.