Description: 

• Assign multiple container groups to one organization and implementing a failover setup: jobs should run on the second container group if the first one hits its quota or the cluster API fails.

• As per the doc, it is suggested to configure the forks setting at the job template level, as this value is passed to the container during execution as outlined here: 

 > https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/using_automation_execution/controller-instance-and-container-groups#controller-container-capacity

Note: Container groups do not use the same capacity algorithm as regular nodes. You must configure the number of forks at the job template level. This setting is then passed to the container at runtime.

• However, when the forks has been set to 0 which means the container group's capacity defaults to the resource quotas of the associated OCP namespace. Now if the OCP API endpoint associated with the first container group becomes unavailable, then there doesn't appear a way for a task to automatically be assigned to the next container group in the list.

Business requirements here: **

• Customer is looking for an approach to assign multiple container groups to a single organization and is looking to implement a setup where jobs are executed on the second container group in sequence if the first one exceeds its quota or if the cluster API becomes unresponsive.