UN automation platform
Shared AWX platforms with controlled team access.
AWX platform modernization
Make the next AWX upgrade a routine operation.
How a legacy AWX platform was rebuilt with the AWX Operator, Git-based configuration, reproducible execution environments and rehearsed upgrades.
The problem
The legacy platform had accumulated configuration through the interface, hand-built execution environments and deferred upgrades. Teams depended on it daily, so migration needed to preserve job behavior and keep cutover reversible.
The target platform
An operator-based deployment on Kubernetes / OpenShift used Kustomize to describe environment differences. Platform resources were synchronized from source, execution environments were built in CI, and access was scoped by team and target.
Validation before cutover
The replacement ran alongside the existing platform. Representative jobs were compared, content was tested with Molecule, synchronization tooling was tested with pytest, and upgrade and rollback procedures were exercised before wider adoption.
The result
Platform state could be reconstructed from Git. Execution environments became versioned and reproducible, access was easier to review, and upgrades followed a rehearsed process rather than relying on undocumented knowledge.
Let’s talk