Hello,
Scenario - 2 containers(say X & Y) of AWX configured in Load balancer setup. Both the AWX UIs pointing to one single DB. Currently in both the AWX UIs, Job templates are configured with execution environment specified as “X”.
Problem - What is the right way (without manual reconfiguration) to configure execution environments if you want to do a switchover to Y when X is down.
Thanks,
Can you elaborate on your use case a little more, specifically why do you need a different EE depending on which AWX pods are running at that time.
execution environment are designed to be agnostic to the AWX deployment in general, so we aren’t seeing why EEs would need to change if your cluster pods change.
Thanks for any additional info you can provide
AWX Team
Hello,
Correcting the problem statement - Its about how to ensure high availability of Instance_groups.
If we have multiple instance groups in a setup then how to configure it in such a way that the job runs on the highly available instance_group only.
I see that AWX allows you to assign multiple instance_groups at templates level/ inventory level/ organization level. But still it picks up the first one in a sequence for execution. If the first instance_group is not available then it doesn’t continue with 2nd one. The job simply fails. How to avoid this situation and manual configuring/reconfiguring of instance_groups ?
Thanks,
Vrunda
can you provide more details on your different instances? are you using remote execution nodes, or are you using container groups to connect to remote k8s clusters?
AWX Team