Hello friends,
Late last year, we announced some upcoming changes to the AWX Project… and that day is finally here. This release is the single biggest change to our application’s architecture and deployment model since conception of AWX. Version 18 represents nearly a year’s worth of work from nearly two dozen contributors.
Below is a high-level overview of the contents of this release. For a full list of changes, see CHANGELOG.md.
Execution Environments
Execution Environments are container images that serve as Ansible control nodes. AWX ships with a default Execution Environment, but you can build your own to suit your needs. To learn more about building your own EEs, see the Ansible Builder documentation.
Ansible 2.11 by default
The default Execution Environment, quay.io/ansible/awx-ee, is based on Ansible 2.11.
If you wish to build your own Execution Environment that uses Ansible 2.9:
- Use quay.io/ansible/ansible-runner:stable-2.9-devel as your EE base image
- Instructions on how to do that with Ansible Builder: https://ansible-builder.readthedocs.io/en/latest/usage.html#build-arg
Removal of Custom Virtual Environments
Custom virtual environments have been removed in favor of Execution Environments.
Introducing the AWX Operator
Starting in version 18.0, the AWX Operator is the preferred way to install AWX. To quickly get up and running see our docs for installing with Minikube.
Removal of Local Docker Installer
The “Local Docker” installer has been removed. If you’re attempting to migrate an older Docker-based AWX installation, see: Migrating Data from Local Docker.