awx-operator VS controller_configuration

We're happy to announce that AWX Version 23.0.0 is now available! We're happy to announce that AWX Operator version 2.5.2 is now available!

So what did I do wrong here ?! I followed the guide step by step (https://github.com/ansible/awx-operator) but still failed.

AH. I checked and found this open issue: https://github.com/ansible/awx-operator/issues/1391

Please see the releases pages for more details: AWX, Operator.

awx has an operator - https://github.com/ansible/awx-operator

I'm now attempting a POC to use k8s, despite having limited experience with it. I've successfully deployed AWX using the https://github.com/ansible/awx-operator on k8s, which includes Postgres. However, I'm unsure how to configure AWX with the plays that we publish in our CI/CD pipeline.

You can look at the operator source code https://github.com/ansible/awx-operator to see exactly what it does.

I have setup AWX Operator from https://github.com/ansible/awx-operator and everything works ok. But there's an annoying warning when running modules from the community.vmware collection.

We're happy to announce that AWX version 21.10.2 is now available! We're happy to announce that AWX Operator version 1.1.3 is now available! This AWX version downgrades a dependency which was causing tracebacks to appear often in the logs of some deployments.

infra.controller_configuration 2.5.1 has been released. This Ansible collection allows for easy interaction with an AWX or Ansible Controller server via Ansible roles using the AWX/Controller collection modules.

The controller_configuration collection version 2.4.0 has been released.

The Infra config as Code collection group will have a Public Office hours meeting on May 11th at 9am EST/1pm UTC. Details here.

one thing is to play to what you know. Also know that collections can be roles, modules, or both. A few biased collections to look at to see the difference would be infra.controller_configuration - a set of roles to implement either the awx.awx collection or ansible.controller collection for doing configuration as code.

multiple collections with grouped roles, then playbooks to execute those roles as needed. You can also do role include like dispatch here to make it more flexible.

The infra collections have had recent updates: * infra.ah_configuration 1.1.0 Automation hub and galaxy_ng configuration. Majorly improved testing and as a result of fixes all modules and roles work on the last 3 versions of galaxy_ng and Automation Hub. * infra.controller_configuration 2.2.5 Various fixes and additions and improvements to collection, including methods to export configuration files from controller to be used by the collection. * infra.ee_utilities 2.0.6 Updated several bugs and add ability to use types in collection requirements for building execution environments

All of the collections in this group have recently released changes. This includes: * infra.controller_configuration 2.1.9 released to be compatible with recently added AWX changes. Changelog here. * infra.ah_configuration 0.9.2 Automation hub and galaxy_ng configuration. Fixed various major errors, including a major publishing error. Changelog here. * infra.ee_utilities 2.0.1 Updated to add several use cases to Execution Environment Creation. * infra.aap_utilities 2.2.2 Update to OCP installer to allow individual components.

For the server configuration, its on the kubernetes side, however for the AWX configuration of projects, job templates, credentials and the like is the redhat_cop.controller_configuration collection. It uses the awx.awx collection or the ansible.controller configuration to interact with the API to manage things in AWX. The collections are built to work with Ansible Automation Controller, but 99.9% of the time its going to work with AWX.