# Hybrid mode not available for instance group in K8 operator installation?

**URL:** <https://forum.ansible.com/t/hybrid-mode-not-available-for-instance-group-in-k8-operator-installation/4906>\
**Category:** Get Help\
**Created:** [April 11, 2024, 5:11pm UTC](https://forum.ansible.com/t/hybrid-mode-not-available-for-instance-group-in-k8-operator-installation/4906 "2024-04-11T17:11:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mimianddaniel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mimianddaniel/32/2123_2.png) [@mimianddaniel](https://forum.ansible.com/u/mimianddaniel)\
**Post date:** [April 11, 2024, 5:11pm UTC](https://forum.ansible.com/t/hybrid-mode-not-available-for-instance-group-in-k8-operator-installation/4906/1 "2024-04-11T17:11:57Z")

</div>

Running 23.7.0 using 2.11.0 operator.  
The document suggests that only difference between the control and hybrid instance is the node\_type. Updating the backend to do this is not ideal, what’s the proper way to perform this from the operator?

---

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [April 11, 2024, 5:20pm UTC](https://forum.ansible.com/t/hybrid-mode-not-available-for-instance-group-in-k8-operator-installation/4906/2 "2024-04-11T17:20:24Z")

</div>

Hybrid node\_types are only available to AAP, not AWX.

[awx/docs/clustering.md - Line 64](https://github.com/ansible/awx/blob/devel/docs/clustering.md?plain=1#L64)

---

<div class="post-metadata">

**Author:** ![mimianddaniel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mimianddaniel/32/2123_2.png) [@mimianddaniel](https://forum.ansible.com/u/mimianddaniel)\
**Post date:** [April 11, 2024, 5:22pm UTC](https://forum.ansible.com/t/hybrid-mode-not-available-for-instance-group-in-k8-operator-installation/4906/3 "2024-04-11T17:22:16Z")

</div>

I read that as well but it doesn’t say why and there is a line that says the only difference between control and hybrid is just the node\_type. It would be nice to get some clarification as to why this is not available in AWX.

---

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [April 11, 2024, 6:07pm UTC](https://forum.ansible.com/t/hybrid-mode-not-available-for-instance-group-in-k8-operator-installation/4906/4 "2024-04-11T18:07:41Z")

</div>

Unfortunately, I can’t really say _why_ it’s this way from a design standpoint. I presume it’s because the downstream BU/RH team requested support for hybrid nodes, and the AWX team implemented the necessary framework upstream. Then the AAP team patches the code with whatever changes are necessary to enable it.

---

<div class="post-metadata">

**Author:** ![mimianddaniel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mimianddaniel/32/2123_2.png) [@mimianddaniel](https://forum.ansible.com/u/mimianddaniel)\
**Post date:** [April 11, 2024, 10:49pm UTC](https://forum.ansible.com/t/hybrid-mode-not-available-for-instance-group-in-k8-operator-installation/4906/5 "2024-04-11T22:49:16Z")

</div>

how many resources allocated to the awx-task is reasonable where you are not running any tasks within the instance anymore?