Execution Environments (EE) and Instance Groups

Execution Environments (EE) and Instance Groups are two distinctly different things. - The EE is the container image that spins up when a Templates is run. There is a specific tool provided by ansible to build the images and its designed to be able to add additional components, like python modules and collections/roles to the running environment. - Instance Groups are more about the environment that the EE will run in. Technically the worker nodes could span multiple clusters, so you could build different Instance Groups based on different clusters. This could be done to force jobs to run in different geographic locations or on special hardware. - In our case, its a bit simpler. Once use case is being able to pass kubernetes secrets or config maps into the running container. Another is mounting azure storage to the contain at job run time. Again these are all things about the environment that the containers run in.

Granting access

EE

This is fairly simple. The Options are make an EE available to One and only One Org or All of the orgs. One the edit page for the EE, leave the Org field black to make it available to everyone.

Instance Groups

Instance Groups can be set at 2 different levels: - Organization - Inventories - Job Templates

For Organizations, navigate to the List of Orgs, edit the desired Org, and click on the search icon for 'Instance Groups' and check the boxes for allowed Instance Groups. As they are selected, they can also be placed in order of preference.