Task Pod In Separate Instance Group

[AwxTaskHelp]

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that AWX is open source software provided for free and that I might not receive a timely response.

Feature type

New Feature

Feature Summary

I have intergeated awx with another application which can occasionally spam awx and trigger many workflows. This can cause the task pod to go out of memory causing more critical workflows to queue in pending state. Rather than just increase the memory and scale the task pods (I have added more task pods) I want to be able to isolate the workflows that are triggered by the other application. I would like to have these workflows use their own task pod so only that job type would experience queuing. When I add more task pods they are all put in the control plane which can not be edited. This means it’s not possible to have jobs scheduled with a dedicated task pod unless you spin up a whole other awx instance (web ui etc).

Select the relevant components

• UI
• API
• Docs
• Collection
• CLI
• Other

Steps to reproduce

Have multiple instances of task pod and try to isolate certain workflow templates to just one task pod

Current results

Scaling up task pods just means scheduling is automatically balanced between for all jobs. I want to give priority to certain jobs/workflows.

Sugested feature result

Be able to move awx task pods to their own instance group so the instance group can be defined by the workflow/job template

Additional information

No response

[jessicamack]

@kdelee are there any workarounds for this or is this a current limitation?