Feature Overview

The execution nodes should be part of the selected instance group only rather than part of two groups i.e. selected group as well as default group.

The current behavior is the execution nodes by default go into the instance group named
'Default' though you can control additional execution group creation and nodes through the inventory.

Ideally, , the nodes should not go on default group if the nodes are part of
specific group.

Background, and strategic fit

Essentially at the moment there is no way of stopping an execution nodes being added to the default instance group every time setup.sh is ran. This is going to be problematic for instances in environments where that execution node will only be able to connect to the a specific (SDX) estate.

Once added to the default instance group every time that node is used for non SDX traffic the connection will fail and cause a failed job, this means the customer will have to login and manually update the default instance group to disassociate the SDX execution node every time setup.sh is ran.