# Are containerized Remote Execution Nodes possible?

**URL:** <https://forum.ansible.com/t/are-containerized-remote-execution-nodes-possible/7504>\
**Category:** Get Help\
**Tags:** awx, ee\
**Created:** [July 26, 2024, 5:55pm UTC](https://forum.ansible.com/t/are-containerized-remote-execution-nodes-possible/7504 "2024-07-26T17:55:14Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![jon-nfc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jon-nfc/32/10748_2.png) [@jon-nfc](https://forum.ansible.com/u/jon-nfc)\
**Post date:** [May 26, 2026, 5:17am UTC](https://forum.ansible.com/t/are-containerized-remote-execution-nodes-possible/7504/12 "2026-05-26T05:17:05Z")

</div>

A few years ago I used this post → [Ability to allow inbound connection to AWX receptor mesh on Kubernetes - #10 by TheRealHaoLiu](https://forum.ansible.com/t/ability-to-allow-inbound-connection-to-awx-receptor-mesh-on-kubernetes/215/10?page=2) to get it working in kubernetes. From memory to change the node from hop to execution was a simple change of one of the receptor cli flags or it may have been when you initially create it within AWX. It was a while ago now.

---

_[View the full topic](https://forum.ansible.com/t/are-containerized-remote-execution-nodes-possible/7504)._
